Section 508 Accessibility
Criteria
|
|
|
(a) When software is
designed to run on a system that has a keyboard, product functions
shall be executable from a keyboard where the function itself or the
result of performing a function can be discerned textually.
|
Supported with exceptions
|
Exceptions include the
following:
-
There are no keyboard equivalent
keys to zoom, pan, lens and highlight the diagram.
-
There are no keyboard keys available
to de-select the observation or variable once it is selected.
-
There are no keyboard equivalent
keys to minimize, maximize, and close the child windows.
|
(b) Applications shall
not disrupt or disable activated features of other products that are
identified as accessibility features, where those features are developed
and documented according to industry standards. Applications also
shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the
product developer.
|
|
The software does not
disrupt or disable any of the keyboard accessibility features incorporated
within the operating system.
|
(c) A well-defined on-screen
indication of the current focus shall be provided that moves among
interactive interface elements as the input focus changes. The focus
shall be programmatically exposed so that Assistive Technology can
track focus and focus changes.
|
Supported with minor
exceptions
|
On-screen indication
of the current focus is provided except in the following cases:
-
In the diagram window, the visual
focus indicator is not prominent.
-
Tab navigation skips over the icon
toolbar. However, the toolbar commands are available from the application
menu.
|
(d) Sufficient information
about a user interface element including the identity, operation and
state of the element shall be available to Assistive Technology. When
an image represents a program element, the information conveyed by
the image must also be available in text.
|
|
Most interface elements,
including menu bar options and shortcut keys, are read by a screen
reader. However, JAWS is not able to read the data tables
|
(e) When bitmap images
are used to identify controls, status indicators, or other programmatic
elements, the meaning assigned to those images shall be consistent
throughout an application's performance.
|
|
Images are used consistently
throughout the interface.
|
(f) Textual information
shall be provided through operating system functions for displaying
text. The minimum information that shall be made available is text
content, text input caret location, and text attributes.
|
|
The software uses standard
operating system functions for displaying text.
|
(g) Applications shall
not override user selected contrast and color selections and other
individual display attributes.
|
|
The software inherits
user-selected contrast and color selections for display attributes
to the extent supported by the platform.
|
(h) When animation is
displayed, the information shall be displayable in at least one non-animated
presentation mode at the option of the user.
|
|
The software contains
no animation.
|
(i) Color coding shall
not be used as the only means of conveying information, indicating
an action, prompting a response, or distinguishing a visual element.
|
|
Color alone is not used
to convey meaning.
|
(j) When a product permits
a user to adjust color and contrast settings, a variety of color selections
capable of producing a range of contrast levels shall be provided.
|
Supported with minor
exceptions
|
The software offers
user options to enable users to choose alternating row colors for
grids to ensure ample color contrast for a range of vision abilities.
|
(k) Software shall not
use flashing or blinking text, objects, or other elements having a
flash or blink frequency greater than 2 Hz and lower than 55 Hz.
|
|
The software uses no
flashing or blinking elements beyond the system caret.
|
(l) When electronic
forms are used, the form shall allow people using Assistive Technology
to access the information, field elements, and functionality required
for completion and submission of the form, including all directions
and cues.
|
|
Compatibility with assistive
technology was assessed using JAWS screen reader version 9.
|