Accessibility Features of SAS Enterprise Case Management 6.2

Overview

SAS Enterprise Case Management 6.2 has been tested against the accessibility standards for electronic information technology that were adopted by the U.S. Government under Section 508 of the U.S. Rehabilitation Act of 1973 (2008 draft proposal initiative update). It was also tested against Web Content Accessibility Guidelines (WCAG) 2.0 levels A and AA, part of the Web Accessibility Initiative (WAI) of the Worldwide Web Consortium (W3C). For detailed information about the accessibility of this product, send e-mail to accessibility@sas.com or call SAS Technical Support.

Documentation Format

Please contact accessibility@sas.com if you need this document in an alternative digital format.

Exceptions to Accessibility Standards

Some exceptions to accessibility standards are documented in the following table.

Note: The JAWS issues occur when JAWS is used with Internet Explorer. Other browsers were not tested with JAWS, unless noted.

Exceptions to Accessibility Standards
Accessibility Issue	Workaround
Keyboard navigation is not supported when you change preference options in the Preferences window. A mouse is required to accomplish this.	No workaround available.
When a new window or dialog box opens, focus is not placed within the dialog box and navigation is not possible using the keyboard alone.	The mouse can be used to place focus in the dialog box. However, items on the main window in the background still receive focus.
There is no visual focus when you close certain messages.	No workaround available.
Items that are not available (dimmed) are able to receive focus.	No workaround available.
Column sorting is not possible with the keyboard.	No workaround available.
High-contrast themes must be manually created.	No workaround available.
Visual indication of focus might be difficult to see in some areas.	No workaround available.
The software requires that style sheets are enabled.	No workaround available.
When you use FireFox, screen readers do not correctly identify the Help and Actions menus.
When you use JAWS with Chrome, many items are not read properly.	No workaround available.
When you use JAWS with Chrome, table reading commands do not function properly with many tables.	No workaround available.
When you use JAWS, extraneous information is read for toolbar buttons.	No workaround available.
When you use JAWS, the expand and collapse arrows for panels are labeled incorrectly and are read as “Unlabeled zero button” by JAWS.	No workaround available.
When you use JAWS, the expand and collapse arrows do not identify what is being expanded or collapsed on entity windows.	No workaround available.
When you use JAWS, the Actions menu for entities is read as “Unlabeled zero button” or "Black down pointing triangle.”	No workaround available.
When you use JAWS, the column manager button is read as “Unlabeled zero button.”	No workaround available.
When you use JAWS, the button for dismissing a notification is read as “Unlabeled zero button.”	No workaround available.
When you use JAWS, calendar edit fields are not sufficiently read, which does not allow screen readers to provide information about what is being edited.	No workaround available.
When you use JAWS, table navigation links are read as “Table go to page link.”	No workaround available.
When you use JAWS, the informational, warning, and error messages displayed at the top of the screen cannot be read.	No workaround available.
When you use JAWS, all relevant information about items contained in the filter panel is not automatically read in some instances.	You can use table reading commands to have JAWS read information associated with some edit fields.