Section 508 VPAT

Subscription Options

Summary Table for Voluntary Product Accessibility Template (VPAT)

Section 508 Requirement Level of Support Remarks and explanations
Section 1194.21 Software Applications and Operating Systems n/a  
Section 1194.22 Web-based Internet Information and Applications Compliant
  • Designed to be accessible and usable to people with disabiltiies form the beginning. Basically eating our own dog food.
  • Use the latest ARIA and HTML5 accessibility techniques to implement WCAG 2.0 Level A and AA requirements.
  • Implement ARIA Landmarks using ARIA 1.1 Authoring Guide Best Practices.
Section 1194.23 Telecommunications Products n/a  
Section 1194.24 Video and Multi-media Products n/a  
Section 1194.25 Self-Contained, Closed Products n/a  
Section 1194.26 Desktop and Portable Computers n/a  
Section 1194.31 Functional Performance Criteria Compliant Tested with:
Section 1194.41 Information, Documentation and Support Compliant with one exception Getting started video is currently not captioned by should be by the end of Septemebr 2017

Section 1194.22 Web-based Internet Information and Applications

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). Compliant Very few images in the user interface.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Compliant with one exception
  • Getting started video will be captioned by the end of September 2017.
  • No other video materials other than the getting started video.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Compliant Colors only used to complement text labels.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Compliant Application will work without stylesheets, but not recommended. Use high contrast setting of operating system.
(e) Redundant text links shall be provided for each active region of a server-side image map. n/a No server-side image maps used in FAE 2.0.
(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. n/a No client-side image maps used in FAE 2.0.
(g) Row and column headers shall be identified for data tables. Compliant
  • Tables are only used for tabular data.
  • Tables also have accessible names using the aria-labelledby attribute to a corresponding heading.
(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. Compliant
  • Tables that have more than one level of headings use the headings attribute to identify headings for the data cell.
  • Each header cell in ables that have more than one level of headings Heading cells have unique ids.
(i) Frames shall be titled with text that facilitates frame identification and navigation n/a No frames or iframes used in FAE 2.0.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. n/a No visual animations used in FAE 2.0.
(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. n/a The web interface is fully WCAG 2.0 Level A and AA compliant. No need for a text only page.
(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. Compliant
  • All form controls and widgets are properly labelled for compatibility with assitive technlogies.
  • All form controls and widgets have keyboard support and visible keyboard focus indicators.
  • Keyboard bindings for widgets are based on the W3C WAI ARIA Authoring Practices Guide 1.1
(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). n/a The applets or plugins used with FAE 2.0.
(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. Compliant
  • All form controls are properly labelled for compatibility with assitive technlogies.
  • Radio button groups used the fieldset/legend to provide a grouping label.
(o) A method shall be provided that permits users to skip repetitive navigation links. Compliant
  • The PayPal SkipTo.js script is used provide keyboard navigation to sections of the document, including to the main content.
  • Headings and ARIA landmarks provide additional methods for assistive tehcnology users to directly navigate to sections of content with FAE 2.0.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. n/a There are no time outs used in FAE 2.0.

Section 1194.31 Functional Performance Criteria

Criteria Level of Support & Supporting Features Remarks and explanations
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. Compliant User interface is written in HTML and compliant with WCAG 2.0 Level A and Level AA requirements.
(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. Compliant User interface is written in HTML and compliant with WCAG 2.0 Level A and Level AA requirements.
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided n/a  
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. n/a  
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. n/a  
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. n/a  

Section 1194.41 Information, Documentation and Support

Criteria Level of Support & Supporting Features Remarks and explanations
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge n/a All product documentation is online in an HTML format the complies to WCAG 2.0 Level A and AA requirements.
(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. n/a All product documentation is online in an HTML format the complies to WCAG 2.0 Level A and AA requirements.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. n/a All product documentation is online in an HTML format the complies to WCAG 2.0 Level A and AA requirements.