Section 1194.22 Web-based Internet information and applications – Detail

VPAT ™

Voluntary Product Accessibility Template^®

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).

Fully Supports

- All images have appropriate alt tags.

- All icons are purely decorative or accompanied by relevant text. Note that the flag and navigation icons used in the input field for the automated phone recorder are not required for functionality, and that the +1 prefix for US and Canada numbers is automatically applied upon field focus.

- The web audio recorder contains controls via HTML and javascript that use text buttons and are both screenreader accessible and keyboard accessible.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Fully Supports

There are no multimedia presentations.

However, playback of audio recordings is present. When an audio recording is played back, it is the same recording the user has created, and so complies with the spirit of the accessibility guideline (that is, there is no playback of audio that requires visual captioning).

(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 Supports

No information is conveyed by color alone.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Fully Supports

HTML is structured to be readable without CSS (e.g., no positioning or structure through CSS, and no information conveyed through background images). Javascript written so that modals re-focus on triggering element when closed, and modals contain appropriate ARIA attribute tags.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not Applicable

No image maps used.

(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

No image maps used.

(g) Row and column headers shall be identified for data tables.

Not Applicable

No data tables used in pages required for user to register and record their name.

(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.

Not Applicable

No data tables used in pages required for user to register and record their name.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Not Applicable

No frames 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.

Fully Supports

No blink or marquee elements used, or animations used.

There is a link to a Adobe's Flash Test Page, which uses a Flash animation, accessible through the 'Problems' tab. The user is given notice that an animation will play on that page.

(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

Pages are compliant with sections (a)-(j),consistent with priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0). Sections (l)-(p) compliance either being verified or in progress.

(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

Known Exceptions:

- modal close dialog buttons read as 'multiplication' by some Assistive Technology. (correction in progress)

(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).

Supports with Exceptions

Download link for Javascript are provided. These are fairly standard components in modern web usage. Compliance of these third-party products is reviewed below:

Java VPAT

(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

Forms are developed such that prompts are maximally proximal to input fields (using placeholder attribute for prompts), and so that input fields are labeled with associated ids.

We provide two options for recording functionality, maximized for accessibility separately and together. The automated phone recorder* allows a visually-impaired user to use audio prompts to record their name. Both the automated phone recorder and web audio recorder can be used with the keyboard alone. However, please note that third-party applications sometimes used with the web audio recorder (in particular, Google's Chrome Browser and an embedded Adobe Flash object) require additional keyboard tabbing outside of our application to use. We have provided a link to instructions for the relevant users.

Known Exception:

- some internal links are not clickable on some screen reader Assistive Technologies. (correction in progress)

*currently available in US and Canada only - more countries coming soon.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Fully Supports

A visible 'Skip Navigation' link precedes all navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports through Equivalent Facilitation

The usual time response issues (e.g., forms that time out) are not present on the site, so the site complies with the spirit of the accessibility guideline. However, the web audio recorder and automated phone recorder both allow a maximum of 10 seconds of recording time.

Equivalent facilitation due to:

1) 10 seconds is usually more than 3 times the sufficient time to record a name.

2) The user can restart/repeat the recording process as many times as needed, and is provided easy-to-use prompts for doing so, for both the web audio recorder and automated phone recorder.