Section 1194.21 Software Applications and Operating Systems - Detail
Voluntary Product Accessibility Template
|
| Criteria |
Supporting Features |
Remarks and explanations |
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (g) Applications shall not override user selected contrast
and color selections and other individual display attributes. |
Supports |
|
| (h) When animation is displayed, the information shall be
displayable in at least one non-animated presentation mode at the option of the user. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
| (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. |
Supports |
|
Section 1194.22 Web-based Intranet and Internet information and Applications - Detail
Voluntary Product Accessibility Template
|
| Criteria |
Supporting Features |
Remarks and explanations |
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). |
Supports |
|
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports |
|
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
Supports |
|
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with exceptions |
The JAMS web client makes all content available even when the associated stylesheets are disabled, however there is some structural information that is only contained within the stylesheet which does degrade the user experience when it is missing. |
| (e)Redundant text links shall be provided for each active region of a server-side image map. |
Supports |
|
| (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. |
Supports |
|
| (g) Row and column headers shall be identified for data tables. |
Supports with exceptions |
Some data tables within the JAMS web client are displayed using ngx-datatable components. While these components do identify column and row headers they may not be identified in a way that is compatible with all AT applications. |
| (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. |
Supports with exceptions |
Some data tables within the JAMS web client are displayed using ngx-datatable components. While these components do associate data cells with column and row headers they may not be associated in a way that is compatible with all AT applications. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supports |
|
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
Supports |
|
| (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. |
Does not support |
While the JAMS web client does fully support most provisions of this section, a text-only page is not available in the case of a potential exception |
| (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. |
Supports |
|
| (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). |
Supports |
The JAMS web client does not require any applet, plug-in or other application on the client system to interpret page content |
| (n) When electronic forms are designed to be completed on-line, 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. |
Supports |
|
| (o) A method shall be provided that permits users to skip repetitive navigation links. |
Does not support |
The JAMS web client allows users to tab through navigation links but there currently is no shortcut to immediately skip them. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports |
|
Section 1194.31 Functional Performance Criteria - Detail
Voluntary Product Accessibility Template
|
| Criteria |
Supporting Features |
Remarks and explanations |
| (a) At least one mode of operation and information
retrieval that does not require user vision shall be provided, or support for Assistive Technology used by
people who are blind or visually impaired shall be provided. |
Supports when combined with compatible AT. |
|
| (b) At least one mode of operation and information
retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print
output working together or independently, or support for Assistive Technology used by people who are visually
impaired shall be provided. |
Supports when combined with compatible AT. |
|
| (c) At least one mode of operation and information retrieval that does
not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or
hard of hearing shall be provided |
Supports |
|
| (d) Where audio information is important for the use of a product, at
least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or
support for assistive hearing devices shall be provided. |
Supports |
|
| (e) At least one mode of operation and information
retrieval that does not require user speech shall be provided, or support for Assistive Technology used by
people with disabilities shall be provided. |
Supports |
|
| (f) At least one mode of operation and information
retrieval that does not require fine motor control or simultaneous actions and that is operable with limited
reach and strength shall be provided. |
Supports |
|
This document is for informational purposes only. MVP Systems makes no warranties, express or implied, in this document.