SAS® Risk and Finance Workbench 3.2

Accessibility Conformance Report

There are several images without complete description in the software.

In the software itself, the UI elements do not rely on presentation alone to convey content. However, visualizations and node diagram content does not pass this criterion.

Content conveyed through presentation is not always conveyed through text or other indicators.

In the software itself, most content conveyed through color is also presented via text. Node diagrams with differing colors have other visual indicators of meaning for sighted users.

There are some places in the software where the keyboard is not supported and the mouse is required. Areas include:

• Cannot access show actions menu items with keyboard
• Items in Workflow cannot be interacted with via keyboard
• Node diagrams can not be navigated using the keyboard alone.
• Preferences cannot be navigated fully via keyboard

Keyboard focus can become stuck in some areas of the software, but the landmarks system can be used to get out of them.

There is no autoplaying content in the software.

There is no content in the software flashing between 5hz and 55hz.

As noted in criterion 2.1.1, many areas of the software do not support keyboard input. However, in areas where keyboard focus is accepted, keyboard focus is visible and tab order is logical. Exceptions to this include:

• Focus resets after changing radio button selection
• Focus goes to the whole node diagram, even though keyboard interaction does not work. Keyboard focus can’t go any deeper than the main object.

There are some links where the immediate context of the link may not be clear.

When user input is required, there are label to describe what is required. This does not pertain to AT interaction. See 4.1.2.

Some parsing errors are present.

There are some portions of the software that do not support screen reader interaction. Some objects may require the user to change their screen reader cursor type. Areas include:

• Node diagram is inaccessible to assistive technology. Since this is such a vital part of the software, screen reader users will be prevented from accomplishing meaningful work in the software.
• Some tables are not read correctly and can not be fully navigated while a screen reader is active. An alternative path is to export using APIs.
• Some drop down menus may not open with the screen reader is active.

There are some areas of the software where the contrast for text is below the 4.5:1 requirement.

Text zooming may truncate some elements depending on pane layout.

The software is a complex web software, and not a set of static pages. As such, there is explicitly only one way to do many of the paths of functionality within the software.

Headings and labels are used throughout the software to describe the current section, component, object, etc. This does not pertain to AT interaction. See 4.1.2.

Focus is drawn and has sufficient contrast throughout most of the software with some exceptions.

If there is an additional language on the page, that section does not have an additional lang= attribute.

When errors are present, there is a description of the issue and potential corrections. Note that this does not apply to AT interaction. See 4.1.2.

The software does not contain a 7:1 theme.

There are some portions of the software that do not support screen reader interaction. Some objects may require the user to change their screen reader cursor type. Areas include:

• Node diagram is inaccessible to assistive technology. Since this is such a vital part of the software, screen reader users will be prevented from accomplishing meaningful work in the software.
• Some tables are not read correctly and can not be fully navigated while a screen reader is active. An alternative path is to export using APIs.
• Some drop down menus may not open with the screen reader is active.

Low vision users should be able to successfully use the software, barring some specific color contrast issues. Text zooming may truncate some elements depending on pane layout.

See WCAG 2.1.1, 2.1.2, and 2.4.3 for more details.

See WCAG 2.1.1, 2.1.2, and 2.4.3 for more details.

Users of a different language shouldn’t have too much trouble. Users with cognitive impairments may not be as successful.

Software is not platform software.

The software does not disrupt OS level accessibility features. The software does support OS level tools such as MouseKeys and FilterKeys. OS level color and contrast settings are not fully inherited and supported, however.

There is no an alternative user interface.

See information in WCAG section

See information in WCAG section

When using the software to create content, it is possible to make it so that output loses accessibility information.

There are some accessibility information elements that will be lost when exporting output to PDF (via Excel export).

There are no prompts in the software advising the user of WCAG 2 A and AA requirements.

There are no provided templates (report styles) and systems in place to enable users to create output with sufficient accessibility information.

Documentation lists accessibility issues and workarounds when available.

See information in WCAG section

See information in WCAG section

All support documentation is available in an electronic version.

SAS Technical Support has information on accessibility related features of software.

SAS Technical Support works with the communication needs of users.

There are some portions of the software that do not support screen reader interaction. Some objects may require the user to change their screen reader cursor type. Areas include:

• Node diagram is inaccessible to assistive technology. Since this is such a vital part of the software, screen reader users will be prevented from accomplishing meaningful work in the software.
• Some tables are not read correctly and can not be fully navigated while a screen reader is active. An alternative path is to export using APIs.
• Some drop down menus may not open with the screen reader is active.

Low vision users should be able to successfully use the software, barring some specific color contrast issues. Text zooming may truncate some elements depending on pane layout.

See WCAG 2.1.1, 2.1.2, and 2.4.3 for more details.

See WCAG 2.1.1, 2.1.2, and 2.4.3 for more details.

There is no content in the software flashing between 5hz and 55hz.

Users of a different language shouldn’t have too much trouble. Users with cognitive impairments may not be as successful.

User information is controlled by user and site admin team.

This software does not produce this type of output.

OS and browser text resizing and zooming work as expected in the software.

There is no sound in the software requiring a visual equivalent.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

There is no audio/video multimedia in the software.

The software works correctly with most assistive technologies. See WCAG 4.1.2 for more information.

There are some portions of the software that do not support screen reader interaction. Areas include:

• Icon tab bar is not read
• Node diagrams are not read by a screen reader. A small part of the software in quantity, but large in impact, thus the differing support level here versus the FPC criteria.

Tables in the software are correctly identified as tables. Table and headers are read correctly. However a screen reader user may have difficulty manipulating interactive tables.

The current values of most objects are read correctly.

Text is read correctly throughout the software. However, text attributes are not presented to assistive technology.

Focus order is consistent throughout most of the software.

As noted in WCAG 4.1.2, there are some events in the software that do not correctly inform a screen reader user.

The modification of some states and properties using assistive technology is read correctly. There are some instances where a state change (from selected to unselected for example) are not sent to assistive technology.

The modification of values using assistive technology is sometimes not possible. Interactive tables are the most common issue.

Software is not platform software.

The software does not disrupt OS level accessibility features. The software does support OS level tools such as MouseKeys and FilterKeys. OS level color and contrast settings are not fully inherited and supported, however.

There are user preferences in the software, but it does not contain the full breadth of specifics listed in this criterion.

See information in WCAG section

See information in WCAG section

When using the software to create content, it is not possible to make it so that output loses accessibility information.

There is no automatic or manual accessibility repair assistance in the software.

There are no provided templates (report styles) and systems in place to enable users to create output with sufficient accessibility information.

See information in WCAG section

See information in WCAG section

See information in WCAG section

See information in WCAG section