The Voluntary Product Accessibility Template (VPAT) is a standardized form developed in partnership by the Information Technology Industry Council (ITI) and the U.S. General Services Administration (GSA) to document a product’s conformance with key regulations of Section 508 of the Rehabilitation Act.
Summary Table
|
||
Criteria |
Level of Support & Supporting Features |
Remarks and explanations |
|
Section 1194.21 Software Applications and Operating Systems |
Not applicable | -- |
|
Section 1194.22 Web-based Internet Information and Applications |
Supports with exceptions | Mostly complaint with few exceptions indicated below. |
|
Section 1194.23 Telecommunications Products |
Not applicable | -- |
|
Section 1194.24 Video and Multi-media Products |
Not applicable | -- |
|
Section 1194.25 Self-Contained, Closed Products |
Not applicable | -- |
|
Section 1194.26 Desktop and Portable Computers |
Not applicable | -- |
|
Section 1194.31 Functional Performance Criteria |
Not applicable | -- |
|
Section 1194.41 Information, Documentation and Support |
Not applicable | -- |
|
||
Criteria |
Level of Support & 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 | Non-text elements are used minimal throughout the system and text equivalents are used when necessary. |
|
(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 | There is no color only indicator used. |
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with exceptions | Pages can be visible/readable. But, page layouts will not be in perfect order. |
|
(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. |
Supports with exceptions | Headers almost always provided with the exception of admin module and maybe in few other places where the list or data is clearly listed as associated to page title. |
|
(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 | Levels used in very few pages and there are linked headers. |
|
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Not applicable | Frames are not 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. |
Supports | No visual effect is used to 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. |
Not applicable | There is no text only page as the nature of this software is data entry, forms and reports. |
|
(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 | -- |
|
(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 with exceptions | HTML standards are applied to all forms and should comply with this rule in most pages if not all. |
|
(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 | -- |