RapidIdentity Product Guide: Legacy UI

Section 1194.22 Web-based Intranet and Internet Information and Applications

Table 4. RapidIdentity Support for Section 1194.22 Accessibility Standards

Accessibility Requirements

Level of Support

Explanations

(a) A text equivalent for every non-text element shall be provided (e.g. via "alt", "longdesc", or in element content).

Supported

RapidIdentity uses alt tags for non-text elements.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

N/A

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supported

RapidIdentity does not solely use color to convey information.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

N/A

(e) Redundant text links shall be provided for each active region of a server-side image map.

N/A

RapidIdentity does not use server-side image maps.

(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.

N/A

RapidIdentity does not use client-side image maps.

(g) Row and column headers shall be identified for data tables.

Supported

RapidIdentity always uses row and column headers where applicable.

(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.

Supported

RapidIdentity does not use more than one column header per column.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Supported

Generally, RapidIdentity avoids using frames. In cases where it does, the “name” tag is used.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supported

RapidIdentity does not use any technology that would cause screen flicker.

(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.

N/A

(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.

Supported

All RapidIdentity content that is dynamically created by a script contains proper markup to ensure accessibility.

(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).

N/A

(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.

Supported

RapidIdentity complies with WCAG 2.0 AA standards.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supported

RapidIdentity uses ARIA landmarks to identify regions of the page (i.e. header, navigation, main content).

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

N/A