MWAS | Content Categories & Standards References | Implementation Guidelines |
1. "A text equivalent for every non-text element shall be provided (e.g., via alt tags, longdesc, or in element content)." | Categories Graphics Links Reference Standards 508 1194.22: 508 a WCAG 2.0: WCAG 1.1.1 IITAA: IITAA 4.1, IITAA 4.2 | Required: Informational graphics have text equivalents (via the alt attribute). Links to long descriptions, in-page or external, are provided when alt attribute descriptions are insufficient, for example, in the case of descriptions of charts or graphic tables. |
Required: Decorative/non-informative inline graphics have alt="" (empty alt). |
Required: Graphics used as links (without accompanying text description) have alt indicating link target. |
Strongly Recommended: When graphic icons accompany link text, for example in a graphical menu, the graphics should get empty alt. Example:
<a href="foo.html"><img src="foo-icon.png" alt=""> Foo</a> |
Recommended: Use CSS to render decorative graphics. |
Resource: Find some helpful guides to writing effective alternative text in the ACT Wiki, under Media Accessibility > Describing Graphics. |
2. "Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation." | Categories Multimedia Audio Video Reference Standards 508 1194.22: 508 a, 508 b WCAG 2.0: WCAG 1.1.1, WCAG 1.2.1, WCAG 1.2.2, WCAG 1.2.3 IITAA: IITAA 6.3, IITAA 7.1, IITAA 7.2 | Required: Synchronized full text captions are provided for publicly available video. - Note: For moving-picture video content, a synchronized verbatim caption is required.
- Note: For voice-over narrated automated slide shows and similar, a static transcript, cued to update upon slide change is required.
- Note: Captions should include speaker identifications and "sound effects"/audio cues, where appropriate.
|
Required: Full text transcripts are provided for publicly available audio-only presentations. Note: Transcripts should include speaker identifications and "sound effects"/audio cues, where appropriate. |
Required: Video or audio does not begin playing on page load. |
Strongly Recommended: Video has secondary audio description, when appropriate to content. Note: A descriptive transcript — one that provides all necessary text equivalents of crucial auditory content (sounds, speaker changes, etc.) and video content (scene and character descriptions, etc.) — is an acceptable alternative to synchronized audio-only audio description. |
Note on when captions/transcripts are required: For non-public video (or audio) with a known and controlled audience, captions (or transcripts) are not required but must be provided within a reasonable time if need for accommodation arises. See the "Requirements" section of the GSU Web Accessibility Policy (PDF) for more information. |
3. "Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup." | Categories Graphics Use of Color Reference Standards 508 1194.22: 508 c WCAG 2.0: WCAG 1.4.1 IITAA: IITAA 3.1 | Required: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
Recommended: Author has tested to ensure colors are distinguishable to users with common forms of colorblindness. Resource:Contrast Analyser. |
4. "Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on black and white screen." | Categories Graphics Use of Color Reference Standards 508 1194.22: N/A WCAG 2.0: WCAG 1.4.1 IITAA: IITAA 3.2 | Required: There is sufficient foreground/background contrast when viewed by someone with low-vision or a color deficit. |
Required: When Windows OS high-contrast mode is enabled, all content and controls remain visible. Informational images rendered via stylesheets, such as those commonly used in buttons and navigation links, are replaced by text equivalents, in order to maintain usability and/or indicate functionality. |
Recommended: Author has tested with a color contrast analysis tool or equivalent to ensure W3C standards for foreground/background contrast are achieved. Resource:Contrast Analyser. |
5. "Documents shall be organized so they are readable without requiring an associated style sheet." | Categories Document Organization and Semantics Reference Standards 508 1194.22: 508 d WCAG 2.0: WCAG 1.3.1 , WCAG 1.3.2, WCAG 1.4.8, WCAG 4.1.2 IITAA: IITAA 1.2, IITAA 1.3, IITAA 17.3 | Required: Turning off stylesheets does not negatively impact content order or make the meaning of previously styled elements ambiguous. Negative example: CSS positions the content for visual reading but the HTML source does not have a logical reading order. Negative example: Stylesheets provided an important visual cue that is not also present in text in the HTML source or rendered DOM. |
Required: Properly nested headings organize the content sections of web pages, including using visually-hidden ("off-left") headings where appropriate to create page semantics. |
Required: Pages have a title element in the head of the document. The title should provide the name of the page and contextual information to help orient the user within the web site. The title should be unique within the site whenever possible. |
Strongly Recommended: Major navigation elements (menus) are implemented as HTML unordered lists. |
Strongly Recommended: Pages declare a base document language using the lang attribute on the body (e.g., lang="en"). Any non-default language text is identified using the lang attribute on the parent element. |
Strongly Recommended: HTML is used "semantically" to organize and help provide meaning to content (e.g., lists are implemented with list elements, block quotes are implemented with blockquote elements, etc.) |
Strongly Recommended: Major content sections are identified by using WAI-ARIA landmark roles. |
Strongly Recommended: Document source and tab order aligns with visual display order. This guideline should extend to pages that reorient content sections (columns, etc.) when displayed at narrower widths, for example in the case of responsive web design accommodating mobile browsers. |
Recommended: It is possible to enlarge page text to twice the default size without loss of functionality or content (clipping) or making it necessary to scroll horizontally to read the content. |
6. "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." | Categories Graphics Links Reference Standards 508 1194.22: 508 a , 508 f WCAG 2.0: WCAG 1.1.1 IITAA: IITAA 5.1 | Required: Clickable regions of client-side image maps are properly identified with alt attributes. |
7. "Redundant text links shall be provided for each active region of a server-side image map." | Categories Graphics Links Reference Standards 508 1194.22: 508 e, 508 f WCAG 2.0: WCAG 1.1.1 IITAA: IITAA 5.2 | Required: Server-side image maps are used only when non-geometric/solely positional input is required and an alternative accessible input method is provided in such cases. |
8. "Row and column headers shall be identified for data tables." | Categories Tables Document Organization and Semantics Reference Standards 508 1194.22: 508 g WCAG 2.0: WCAG 1.3.1, WCAG 1.3.2 IITAA: IITAA 11.1, IITAA 17.1 | Required: Data tables identify row and column headers using the tag. |
Required: If tables are used for layout, a logical reading order is maintained. |
Strongly Recommended: Summary attribute is used to explain the purpose and structure of the table. |
Strongly Recommended: Caption element is used to provide a descriptive title for the table. |
Recommended: HTML tables are used for organization of tabular data, primarily, with CSS used for layout. |
9. "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." | Categories Tables Document Organization and Semantics Reference Standards 508 1194.22: 508 h WCAG 2.0: WCAG 1.3.1 IITAA: IITAA 11.2 | Required: Simple HTML data tables (that, is, not layout tables) have scope (row or col) set on table header cells. |
Strongly Recommended: Complex HTML tables (i.e., those with more than a single column or row header and those with complex row or column spans) use headers and id attributes to associate data cells with header cells |
10. "Frames shall be titled with text that facilitates frame identification and navigation." | Categories Document Organization and Semantics Reference Standards 508 1194.22: 508 i WCAG 2.0: WCAG 4.1.2 IITAA : IITAA 12.1, IITAA 12.2 | Required: Frames and iframes have title attributes identifying their purpose and/or briefly describing their content. |
Recommended: Use of hidden frames or iframes is avoided. |
Recommended: iframes or CSS alternatives are used in preference to frames. |
11. "Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz." | Categories Graphics Dynamic Content Multimedia Reference Standards 508 1194.22: 508 j WCAG 2.0: WCAG 2.3.1 IITAA: IITAA 8.2 | Required: No page content or graphic flashes faster than three times per second. |
12. "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." | Categories Keyboard Accessibility and Focus Use of JavaScript Dynamic Content Reference Standards 508 1194.22: 508 l WCAG 2.0: WCAG 1.3.1, WCAG 4.1.2 IITAA: IITAA 13.1, IITAA 13.2 | Required: Scripted elements and/or "widgets" are accessible to the keyboard, with all focusable elements being able to be activated/utilized solely via the keyboard. |
Required: Scripted elements and/or "widgets" are coded so that they work effectively with screen readers. |
Strongly Recommended: W3C WAI ARIA Authoring Practices are followed for scripted elements and widgets. Resource: Model examples are at OpenAjax Accessibility Example. Dojo A11y Requirements provides general guidelines and testing procedures. |
13. "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 standards 1-9 of this document." | Categories Plug-ins Keyboard Accessibility and Focus Multimedia Reference Standards 508 1194.22: 508 k WCAG 2.0: WCAG 1.1.1, WCAG 2.1.2 IITAA: IITAA 14.2 | Required: Plug-in based widgets (Flash, Silverlight, Java, etc.), menus, or other controls embedded in the web site have functionality that complies with standards 1 through 9 of MWAS or a functionally equivalent form of access is provided (e.g., Widgets provide HTML-based, keyboard accessible primary or alternative controls). |
Required: Plug-in based widgets do not "trap" the keyboard/prevent keyboard navigation from moving out of or away from the widget. |
Strongly Recommended: PDF, EPUB, PowerPoint, and other document types linked to within the hosted web site meet appropriate accessibility standards (e.g., PDF is "tagged," PowerPoint is mostly text-based with graphics adequately described, EPUB has a proper document structure with videos captioned and images described, etc.). |
Recommended: Plug-ins required for display or functionality of content are readily available (via link on page or (verified) automatic functionality of web browser). |
14. "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." | Categories Forms Use of JavaScript Reference Standards 508 1194.22: 508 n WCAG 2.0: WCAG 1.3.1, WCAG 2.1.1, WCAG 2.4.6, WCAG 3.3.2 IITAA: IITAA 4.1, IITAA 10.1, IITAA 10.2, IITAA 10.3 | Required: All form elements are able to be utilized fully via keyboard. |
Required: Input fields are associated with labels via "for-id" syntax (title attribute used alternatively, when necessary/by visual requirement) and buttons or button inputs are properly labeled (via encapsulated text or value attribute, respectively). |
Required: If a traditional visual challenge CAPTCHA is used (not advised), an audio challenge alternative is provided and/or a method requiring only text-to-speech output is provided. |
Strongly Recommended: Fieldsets with short descriptive legends group associated radio buttons or check boxes. |
Strongly Recommended: Order of form elements flows logically and associated elements are proximate and in a logical order. |
Strongly Recommended: Form errors are indicated by focusing the errors list on page submit or by focusing first error field and ensuring error message is accessible to a screen reader user by using aria-labelledby or other associative labeling method |
Strongly Recommended: Form required fields are identified textually (via alt on an image of an asterisk, for example) and/or through both aria-required and required attributes. |
Strongly Recommended: Help prompts in forms are accessible to a screen reader and properly associated with the relevant field, using aria-labelledby or other associative labeling method. |
Strongly Recommended: Dynamic, scripted elements within a form (contextual reveals, etc.) do not disrupt form fill out and are tested to be screen reader accessible. |
Recommended: Users are able to confirm and edit long/multi-page form changes before submitting. |
Recommended: Form submission errors are indicated with text proximate to the field and associated with aria-labelledby or other associative labeling method |
Recommended: Forms do not use links for buttons. |
15. "A method shall be provided that permits users to skip repetitive navigation links." | Categories Document Organization and Semantics Keyboard Accessibility and Focus Reference Standards 508 1194.22: 508 o WCAG 2.0: WCAG 2.4.1 IITAA: IITAA 9.2 | Required: A method to skip long lists of links, such as navigation, is provided (e.g., "skip to main content" link is first focusable page element)
Note: MWAS 5 recommends a heading structure and use of ARIA landmark roles. These may provide certain assistive technologies adequate means for skipping repetitive navigation. Nevertheless, for some users, for example, those with motor impairments, it is very helpful to provide visible skip navigation to allow for a convenient means to bypass top level navigation and move straight to content.
Note: For a model implementation of skip links, see Back to Basics: Skip to Main Content Links. |
16. "When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required." | Categories Forms Dynamic Content Reference Standards 508 1194.22: 508 p WCAG 2.0: WCAG 2.2.1 IITAA: IITAA 8.1, IITAA 16.1, IITAA 16.2 | Required: The user is given an accessible method to extend time when a timed response is required. |
Strongly Recommended: The user is given an accessible method to extend the browser "session." |
Strongly Recommended: The user is given an accessible means to pause automatically moving, rotating, updating, or scrolling content. |
Strongly Recommended: Do not automatically refresh the page. |
17. "Do not change the current window without informing the user." | Categories Keyboard Accessibility and Focus Use of JavaScript Reference Standards 508 1194.22: 508 l WCAG 2.0: WCAG 3.2.2, WCAG 3.2.5 IITAA: IITAA 9.4, IITAA 13.3, IITAA 13.4 | Required: The user expects all changes of cursor focus on a page because the user initiated the change purposefully. (e.g., an in-page anchor link is clicked, the screen scrolls and caret focus moves to the anchor.) |
Strongly Recommended: The user is aware of significant changes to page content. (e.g., a new section of content dynamically populates; this change is readily discoverable by the user, regardless of technology being used to access the page (screen reader, etc.).) |
Strongly Recommended: Pop-open dialogs are indicated by moving focus to the dialog and escaping/closing the dialog returns focus to original location on the page. |
18. "Clearly identify the target of each link." | Categories Keyboard Accessibility and Focus Links Multimedia Reference Standards 508 1194.22: N/A WCAG 2.0: WCAG 2.4.4 IITAA: IITAA 9.1 | Required: Link text is understandable out of context on the page (no use of "click here," "more…", or links that are URLs (except when identifying resources for purposes of printing)). |
Required: Keyboard focus is clearly visually indicated (e.g., when tabbing through a page). |
Required: All focusable links and controls are able to be utilized fully via the keyboard. |
Strongly Recommended: A link that loads an external application, PDF, or other media has that application identified with accessible text (e.g., "my file (PDF)"). |
Strongly Recommended: When creating links, the title attribute should only be used when there is a compelling need for extra information to be conveyed, not merely to duplicate link text. The tooltip created by title values is not accessible to keyboard alone, and when hovered with the mouse can obscure adjacent content. If title on links is used, the link text must be repeated, first, with the extra information coming afterward. |
19. "An accessible mirror page (e.g. text-only or non-Flash) with equivalent information or functionality, can be provided to make a web site comply with this policy, when compliance cannot be accomplished in any other way. The content of mirror pages must be updated whenever the primary page changes." | Reference Standards 508 1194.22: 508 k WCAG 2.0: Conforming Alternate Version definition IITAA: IITAA 18.1 | Required: Separate, up-to-date, accessible "mirror pages" are used only as a last resort. See the section on "Exceptions" in the GSU Web Accessibility Policy (PDF) for more information. |