(a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).
All images that are used to convey meaning to a user have appropriate ALT tags
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
Automatic captions are provided that are synchronized with the playback of multimedia presentations.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
Color is not exclusively used to convey meaning.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
HTML remains in the correct order when a given CSS is disabled.
(e) Redundant text links shall be provided for each active region of a server-side image map.
Server-side image maps are not used within the application.
(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.
Client-side image maps are not used within the application.
(g) Row and column headers shall be identified for data tables.
Table headers have appropriate row and column headers.
(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.
This type of table is not utilized within the application.
(i) Frames shall be titled with text that facilitates frame identification and navigation
Frames and iFrames have appropriate titles.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
No pages within the site have elements that cause 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.
The existing web application and site meets compliance and hence an equivalent text-only page is not required.
(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 with Exceptions
In all tested features within scope show action elements as text with the exception of the following buttons: maximize window, minimize window.
(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).
No pages within the site rely on applets or plug-ins as their exclusive means of performing the tasks. For example, all components support HTML5 for user tasks.
(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.
For electronic forms, HTML tags for ALT and TITLE are used to convey meaning.
(o) A method shall be provided that permits users to skip repetitive navigation links.
In the tested features in scope, not repetitive navigation links were identified.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
No timed response elements are used within the application.