Criteria
|
Level of Support
|
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 with exceptions
|
Much of the non-text navigation and functional elements are accompanied by text descriptions. Some non-navigation, non-functional visual elements, such as analytics graphs and social media posts may not be accessible to assistive technology.
Additionally, when users submit non-text content (e.g., social media content), admin users have the option to add alternative text.
|
(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
|
All information in Gigg where data is conveyed with color also includes another indicator that is not color-based.
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
|
Supports with exceptions
|
As Gigg is a web-based application (not a document), the UI associated with its editor relies heavily on the use of associated style sheets.
|
(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
|
|
(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
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation
|
Not applicable
|
|
(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
|
|
(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
|
|
(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
|
|
(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
|
|
(o) A method shall be provided that permits users to skip repetitive navigation links.
|
Supports with exceptions
|
Gigg users must tab through repetitive links as there is no skip to main content.
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
|
Not applicable
|
|