VPAT
When you file register and complete put on a file a Vountary Product Accessibility Form for your site and your products you will be placed in the Buy Accessible Database used by federal government purchasing agents.
If your company has a website this is the criteria you need to meet:
| 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). | Review via software designed to locate and display any missing for human review any non-text tag without an "alt" attribute. | Although care is taken during the development process to ensure that all non-text items have meaningful "alt" or when needed "longdesc" attributes testing is done after page completion for verification. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | When multimedia is used a meaningful alternative will be available, synchronized where practical. | Not all multimedia lends itself to synchronization, if that is the case then an accessible text based version will be available. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Mark-up will be used to create page structure that conveys all information necessary to the function of the page. | Stylesheets which provide color values are used to provide a more asthetic display and are independent of document structure. |
| (d) Documents shall be organized so they are reRehabilitation Act of 1973ble without requiring an associated style sheet. | Mark-up will be used to create page structure that is logical and reRehabilitation Act of 1973ble without stylesheets. | Stylesheets are used to provide a more asthetic display and are independent of document structure. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | WiserWays does not use server side image maps on sites. | At this time WiserWays sees no reason to use server side image maps. In the event that a legitimate need for one arises WiserWays will follow its policy of always providing a text based site map on each website created. |
| (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. | Yes, if an image map is used. | As of this date image maps if used have all been client-side using geometric shapes. |
| (g) Row and column headers shall be identified for data tables. | All data tables use table headers. | When appropriate individual data cells will have header identifiers with-in the markup. |
| (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. | Will be used where applicable. | In the event that there are multiple logical levels in a data table header information will be associated and row information will be associated where appropriate. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation | WiserWays does not use frames as a general practice. Where used each page and frame shall be titled. | WiserWays always provides a site map linked to each page within any site developed. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | None have been created by WiserWays. | If such a page should appear it would immediately be redesigned to remove any such 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. | WiserWays makes every effort to ensure that all pages within a site provide information and function in a manner that complies with § 508. | In the event that any page cannot be made to comply an alternative text only page that provides equivalent information and function will be provided. |
| (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. | In the event that Javascript or other scripting is used for navigation or other function for interface elements a <no script> tag will be utilized to provide alternative access to such interface elements. | All pages with-in a WiserWays created website have links to text based naviation via the site map. A link to by-pass the script navigation to enable a jump directly to the sitemap or other text based navigation. |
| (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). | In most cases server side testing will be utilized to test for the presence of applets, plug-ins or other application (plug-in). Where no such plug-in is found a page with an alternate that does not require any plug-in. | If there is a plug-in available that complies § 1194.219(a) through (l) with but not installed a link to such plug-in and a link to the page that requires the plug-in shall be included on the alternative page served. |
| (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. | Form fields will be in a logical tab order and all information necessary to properly complete the form will be viewable on the page or within the structural mark-up. | In some cases tool tips will be used in others text descriptions will be used where a tool tip would not provide sufficient information for those using Assistive Technology. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Where possible mark-up will place repetitive navagation at the end of the web page in the mark-up regardless of where on the page it displays visually. | This is usually accomplished using CSS. If positioning vis CSS is inappropriate for the site then anchor links to skip to content and to return to the navigation will be included. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Timed responses will not be used without a specific need for and the ability to extend time to response time shall be included if a timed response if needed. | The only timed responses currently in use are security features in limited access areas of websites. Timeouts have been set to accomodate those with impaired mobility. |
Note to 1194.22: 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.