(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
|
Getting started video is captioned.
|
(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.3.
|
(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.3.
|
(g) Row and column headers shall be identified for data tables.
|
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
id s.
th elements are used to identify table header cells.
- For complex data tables the
headers attribute is used to identify table header cells.
|
(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
id s.
th elements are used to identify table header cells.
- For complex data tables the
headers attribute is used to identify table header cells.
|
(i) Frames shall be titled with text that facilitates frame identification and navigation
|
n/a
|
No frames or iframes used in FAE 2.3.
|
(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.3.
|
(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.3.
|
(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.3.
|
(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.3.
|