Section 1194.22 Web-Based 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 (for example, via “alt,” “longdesc,” or in element content). |
Fully supported. |
The user can provide alternative text, allowing applications which support this feature to utilize it. |
(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. |
Fully-supported. |
This requirement is easily accommodated with the design of a page. |
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Fully-supported. |
Tagged PDF & PDF/UA output allows the entire document to be structurally interpreted by software that supports such features |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not applicable |
. |
(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. |
Not applicable |
. |
(g) Row and column headers shall be identified for data tables. |
Fully-supported. |
Tagged PDF & PDF/UA output allows the entire document to be structurally interpreted by software that supports such features. |
(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. |
Fully-supported. |
Tagged PDF & PDF/UA output allows the entire document to be structurally interpreted by software that supports such features. |
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Fully-supported. |
This requirement is easily accommodated with the design of a page. Tagged PDF & PDF/UA output allows the entire document to be structurally interpreted by software that supports such features. |
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2Hz and lower than 55Hz. |
Not applicable. |
. |
(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. |
Not applicable. |
. |
(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. |
Not applicable. |
. |
(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). |
Not applicable. |
The application is designed to create PDF to be deployed, possibly in web based situations. The application that contains the PDF should provide the compatible link, not the PDF. |
(n) When electronic forms are designed to be completed online, 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. |
Fully supported |
Tagged PDF & PDF/UA output allows the entire document to be structurally interpreted by software that supports such features. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Not applicable. |
. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not applicable |
. |