Web-based Internet information and applications
| 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 | All the images in the Platform will be labeled. |
| b. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not Applicable | |
| 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. Redundant text links shall be provided for each active region of a server-side image map. | Supports | |
| e. 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 | |
| f. Row and column headers shall be identified for data tables. | Supports | All the page titles, section headings, and labels for UI controls identify the topic of the content. |
| g. 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 | |
| h. Frames shall be titled with text that facilitates frame identification and navigation. | Supports | |
| i. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supports | |
| j. 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. | Supports | The application fully supports this but some of our content may include tables as images with no text alternative. |
| k. 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 | This has been tested with NVDA. |
| l. 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). | Not Applicable | No Plug-ins are needed |
| m. 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 | The application fully supports this but some of our content may include tables as images with no text alternative. |
| n. A method shall be provided that permits users to skip repetitive navigation links. | Supports | |
| o. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Supports with Exceptions | In Study mode, the user can choose the amount of time needed. In Timed mode, the user can see the countdown timer, but cannot ask for more time. |
Note. The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.
Return to the menu: VPAT™ Voluntary Product Accessibility Template®