Exceptions to Accessibility Standards
|
|
|
Sometimes, you cannot
use the keyboard to sequentially navigate through the interface and
move the focus in a meaningful order.
|
No workaround is available.
|
The SAS High Contrast
theme has a few unresolved focus and contrast issues.
|
For contrast issues,
select a different theme, and then press Ctrl+~ to invert the colors.
|
The SAS Light theme
and SAS Dark theme might not provide sufficient color contrast for
some users.
|
Use the SAS Corporate
theme or the SAS High Contrast theme.
|
Contrast is insufficient
on some UI elements.
|
Use the SAS Preferences
Manager to change the theme to the SAS High Contrast theme.
|
JAWS cannot read some
of the controls in the application, such as images, icons, and buttons.
|
No workaround is available.
|
JAWS cannot read the
tooltips of items in trees, lists, and menus.
|
No workaround is available.
|
JAWS refers to table
controls as list boxes.
|
When JAWS reports that
a control is a list box, keep in mind that it might actually be a
table.
|
JAWS can sometimes read
controls that have been disabled.
|
No workaround is available.
|
JAWS cannot read two-column
property tables.
|
No workaround is available.
|
JAWS does not correctly
read the information in a table:
-
JAWS cannot read the column headings
of a table.
-
When table cells are not editable
and the focus is on the body of the table, JAWS reads an entire row
at a time instead of cell by cell.
-
When table cells are editable and
the focus is on the body of the table, JAWS reads only the first row
of the table. If you use the arrow keys to select a cell or row, then
JAWS does not read anything. If you press Enter to edit a cell, then
JAWS reads the row that contains the edited cell.
|
No workaround is available.
|
When a table cell is
selected and you press Home, End, Page Up, or Page Down, the focus
moves to the first displayed column, regardless of which column you
were in.
|
Use the arrow keys to
navigate through the cells of the table.
|
You cannot use the keyboard
to scroll to the left and the right in some tables.
|
No workaround is available.
|
You cannot use Shift+F10
to open a pop-up menu.
|
Use Shift+F9 to open
pop-up menus that are created for the SAS application. The generic
menu that is provided by the Flash player cannot be opened by Shift+F9.
Note: If you press Shift+F10 in
Internet Explorer and no pop-up menu is available, the browser moves
the focus to the File menu for the browser
tab. To return focus to the application area of the browser window,
press Esc.
|
You cannot use the keyboard
to access the close (x) button that is in the top right corner of
a tab.
|
Make sure that the focus
is on the tab, and then press Delete to close the tab.
|
Visual focus for the
menu bar is indicated with an outline around the entire menu bar instead
of around individual menus.
|
To select individual
menus, use the left or right arrow key.
|
Sometimes, you cannot
use the Tab key to move the focus to the application area of a web
browser (that is, the part of the browser window that is controlled
by the Flash player).
|
The following workaround
is applicable to Internet Explorer only.
Press Ctrl+ number,
where number is the ordinal
position of the application’s tab in the set of tabs that are
open in your browser window. Then press Tab to move the focus to the
application area.
|
If you tab to an item
that is partially or entirely off-screen, the item is not automatically
scrolled back into view.
|
Sometimes, you can use
the arrow keys or the Tab key to scroll the item back into view.
|
When you use the Ctrl+plus
sign keyboard shortcut to zoom in, some portions of the interface
can become hidden from view.
|
Use the keyboard to
access the hidden parts of the interface.
|
The Ctrl+plus sign and
Ctrl+minus sign keyboard shortcuts for zooming in and out do not work
on some menus unless the menus are first opened.
|
Open the menu before
you use the keyboard shortcut.
|
The Ctrl+plus sign and
Ctrl+minus sign keyboard shortcuts for zooming in and out do not work
on all elements in the application window (for example, tooltips and
button labels).
|
No workaround is available.
|
You cannot use the keyboard
to access the color blocks in the Recently used section
of the color selection control.
|
No workaround is available.
|
JAWS does not explain
how to operate a drop-down list and drop-down menu.
|
JAWS refers to these
controls as either "button", "button menu", or
"combo box". In addition to using Ctrl+down arrow to open
these drop-down lists and menus, you can also activate buttons and
some button menus by pressing spacebar. Pressing spacebar either opens
the control or selects the default item.
|
When you use the down
arrow to scroll through the items in a "combo box," any
item that opens a secondary window will do so when you scroll down
to it. This prevents you from navigating to items that are farther
down in the drop-down list.
|
Press Ctrl+down arrow
to scroll through the items in the drop-down list, and then press
Enter or Tab to make a selection.
|
JAWS cannot read the
content selection tree.
|
No workaround is available.
|
JAWS incorrectly states
that you should use Ctrl+Tab to switch tabs.
|
To switch from one tab
to the next, press the left or right arrow key and then press Enter
or spacebar.
|
When JAWS is running,
pressing the up and down arrow in a number selector causes your browser
to crash.
|
Enter the number instead
of using the arrow keys to select it.
|
You cannot determine
which cell in a table row has the focus unless the cell is in Edit
mode.
|
No workaround is available.
|
When a date field with
a calendar button is displayed in a table cell or selection list,
sometimes you cannot move the cursor into the field or move the focus
to the calendar button.
|
No workaround is available.
|
When JAWS is running,
some drop-down menus do not work correctly with the keyboard.
|
Changing the JAWS cursor
mode (press Insert+Z) can sometimes help.
|
In some charts, graphs,
and diagrams, color is the only means for conveying certain types
of information.
|
You can use SAS Theme
Designer for Flex to create custom colors that are easier for low-vision
and color-blind users to discern.
|
In the Manage
Favorites dialog box, the Delete, New,
and Close icons are not read by a screen
reader.
|
No workaround is available.
|
In the workspace area
of the dashboard viewer, no content is read by a screen reader.
|
No workaround is available.
|
In the workspace area
of the dashboard designer, the icons to create a new object are not
labeled for use by a screen reader.
|
For each icon, the text
label that is one tab stop forward can be read by the screen reader.
|
Screen reader does not
read the toolbar icons in the Library section of the dashboard designer.
|
No workaround is available.
|
When you are creating
a new object in the dashboard designer, the screen reader does not
indicate required fields in the Properties pane.
|
No workaround is available.
The following properties are required, depending on the object that
you are creating:
-
New dashboard: Width, Height, Layout
-
New indicator: Width, Height, Display,
Graph style, Indicator data name, Range name, Range value, X-axis
value, Bar value, Bullet value
|
When you are creating
a new range in the dashboard designer, the screen reader cannot read
any content in the workspace.
|
No workaround is available.
|
The screen reader reads
parts of the Create an indicator dialog box
incorrectly, making it harder to identify the Indicator
data field as a required field.
The Indicator
data field is silent. The Browse and New buttons
are read as the previous Indicator data field,
along with the correct label for the selected button.
|
The location of the Indicator
data field is indicated by the silent space before the Browse button.
|
If you reverse tab (Shift
+ Tab) through the fields in the Create an indicator dialog
box, the screen reader does not read the Display type field.
|
Forward tab through
the dialog box to correctly read the Display type field.
|
When you are creating
a new indicator data object, the screen reader does not read the first
editable field in the workspace.
|
No workaround is available.
Depending on the data source that you select for the indicator data,
the following fields are not read by the screen reader:
-
For the Information
map data source, the Information map field
is the first editable field.
-
For the SQL query data
source, the SQL query field is the first
editable field.
-
For the Stored process data
source, the Stored process field is the first
editable field.
-
For the Table data
source, the Table field is the first editable
field.
|
Browser magnification
settings have no effect on dashboard content.
|
To magnify dashboard
content, you must use a third-party screen magnifier.
|
Landmarks are not enabled
for SAS BI Dashboard.
|
Use the tab key to navigate
the application.
|
When you are creating
a new indicator data object in the dashboard designer, the menu for
the Data source field lists the available
data sources with a brief description. If you use a screen reader,
the data source names are read, but the descriptions are not read.
|
For information about
the types of data sources that are available for creating indicator
data, see SAS BI Dashboard: User's Guide.
|