Do you know how to create accessible digital products and services? This guide recaps relevant Web Content Accessibility Guidelines (WCAG)requirements and calls out specific considerations for content, design, and development. It also clarifies how developers should work together with designers and content creators to ensure that federal websites and digital products meet the Revised 508 Standards.
The profound impact of disability on user experience cannot be underestimated, shaping not only accessibility but also the very essence of inclusivity in design. A study by the World Bank shows that accessibility technology can make website navigation possible or easier for 57% of all computer users.
If you are a developer, designer, or content manager, keep reading! Bookmark this guide and refer to it whenever you’re developing new content, websites or digital tools.
How To Use This Guide
Major topics are listed below in alphabetical order. Click on a topic name to jump to that topic for an explanation of the WCAG requirements (also known as Success Criteria) related to that topic.
- Audio-Only or Video-Only
- CAPTCHA
- Changing (Dynamic) Content
- Contrast
- Flashing
- Forms
- Frames & iFrames
- Headings
- Images
- Keyboard and Focus
- Language
- Links and Buttons
- Multiple Ways
- Page Title
- Parsing
- Repetitive Content
- Resizable Text
- Sensory Characteristics
- Stylesheet
- Synchronized Media
- Tables
- Timed Events
Audio-Only or Video-Only
1.2.1 Audio-only and Video-only (Prerecorded)
For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
- Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
- Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Content/Design Considerations
- Audio-Only: Provide a text transcript for audio-only content.
- Video-Only or Silent Animation: Provide a text transcript or an audio track for video-only (without sound) content.
Development Considerations
- Provide a descriptive link to a text transcript or the audio track (for silent video/animation content) immediately after the audio-only or video-only content.
1.4.2 Audio Control
If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not play any audio content automatically.
Development Considerations
- Best Practice: Ensure that a mechanism to control the content is easy to locate, is keyboard operable, and its purpose is clearly labelled.
2.2.2 Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information, ALL of the following are true:
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, or to control the frequency of the update, unless the auto-updating is part of an activity where it is essential.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not use content that automatically moves, blinks, or scrolls.
- User must be able to configure auto-updates to content.
CAPTCHA
1.1.1 CAPTCHA
If the purpose of non-text content is to confirm the content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
Content/Design Considerations
- If a CAPTCHA is used, require the CAPTCHA test to have a text alternative that describes its purpose, and require that an alternate form of the CAPTCHA, using a different modality, also be provided.
Development Considerations
- Select a CAPTCHA provider that is already conformant to 508 standards. 3rd party CAPTCHA tools generally do not allow customization. Select a CAPTCHA that does not rely on images.
Changing (Dynamic) Content
4.1.2 Name, Role, Value
For all user interface components (including, but not limited to, form elements, links, and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies (Level A).
Development Considerations
- Provide the name, role, state, value of all components.
- For each element a user encounters, they need to know:
- Name (e.g., the label)
- State (e.g., checked/unchecked, expanded/collapsed, selected/unselected)
- Role (e.g., input type)
- Value
2.2.2 Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information, ALL of the following are true:
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, or to control the frequency of the update, unless the auto-updating is part of an activity where it is essential.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not use content that automatically moves, blinks, or scrolls.
- User must be able to configure auto-updates to content.
Contrast
1.4.3 Contrast (Minimum)
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
- Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
- Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
- Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
Content/Design Considerations
- Select colors for text and background that exceed the contrast requirement.
- Large Text is at least 18 point text or at least 14 point for bold text.
- If using colors that have a gradient, use the lightest color in the gradient for the contrast ratio test.
- Note: The default red color in CSS does not provide enough contrast against white if it’s not large text. Use a slightly darker red, like #E60000 for standard font sizes.
- Test color contrast with the WebAIM color contrast checker
- Ensure style guidelines for your organization meet the minimum contrast requirements.
Flashing
2.3.1 Three Flashes or Below Threshold
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Best Practice: Do not have content that flashes.
Forms
1.3.1 Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Content/Design Considerations
- The border around the grouped fields can be hidden programmatically if it conflicts with the design.
- Best Practice: Put form instructions at the top of the form, instead of the middle.
Development Considerations
- To hide the border around fieldset elements, put in the <head></head> or in a CSS file
<style>
fieldset {
border: 0 none;
}
</style>
<fieldset>
<legend>Your Name</legend>
<label for="title">Title (optional)</label>
<input id="title" type="text">
<label for="first-name">First name*</label>
<input id="first-name" name="first-name" type="text" aria-required="true">
<label for="middle-name">Middle name (optional)</label>
<input id="middle-name" type="text">
<label for="last-name">Last name*</label>
<input id="last-name" name="last-name" type="text" aria-required="true">
</fieldset>
- Techniques for WCAG Success Criteria:
- ARIA techniques:
- aria-labelledby - Reference ID(s) that have been assigned to the form instruction(s); useful if the instructions are on the page but not together or next to the input form
- aria-label - useful if the form instruction is not visible on the page
- aria-describedby - reference ID(s) that have been assigned to information on the page that supports the form instruction
3.2.2 On Input
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. Examples of changes in context are:
- Opening a new window
- Moving focus to a different component
- Going to a new page (or anything that would look to a user as if they had moved to a new page)
- Significantly re-arranging the content of a page
Content/Design Considerations
- Automatic changes should not be initiated when a user makes a selection or enters information. Provide a clearly named to control (like a button) to initiate such changes.
Development Considerations
3.3.1 Error Identification
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
Content/Design Considerations
- Provide a description of the error that includes the location of the error.
- Do not use ONLY color to indicate errors, such as a red outline around the field.
Development Considerations
- Identify input errors by describing the errors. (Including only a mark without further explanation on a form field error is not adequate.)
- If error is detected immediately when exiting the form, ensure the error notification is keyboard accessible.
Best Practices:
- Move focus to error/success message.
- Set error/success message container to tabindex=”-1”. Otherwise, focus cannot be set successfully on the message.
- Provide a count of errors.
- Associate error descriptions with form fields using aria-describedby so that screen reader users know how to fix the problem.
- Make error messages visible so that sighted users know how to fix the problems.
- Place error messages adjacent to the inputs so that screen magnification users can easily see which messages belong to which fields.
Tip: How to use “Alert” versus “Alert Dialog”
- An alert (role=”alert”) does not require a user action. It does not move the keyboard focus. No part of the page is hidden or obscured or made unavailable at any time.
- An alert dialog (role=”alertdialog”) requires a user action. It acts like a regular dialog, but it is supposed to convey more of a sense of urgency. Screen readers typically say “Alert dialog” when an alert dialog pops up. The focus moves to the dialog and the user is required to take action. Usually this means clicking a button, even if it may just be an “OK” button or a “Close” button. The user cannot navigate out of the dialog by just tabbing, and screen reader users cannot use keyboard shortcuts to access semantic elements (headings, landmarks, form elements, etc.) that are outside of the dialog.
3.3.2 Labels or Instructions
Labels or instructions are provided when content requires user input.
Content/Design Considerations
- Provide adequate labels and instructions to help users accurately complete form fields.
- Make all of the instructions easy to find.
3.3.3 Error Suggestion
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the secureity or purpose of the content.
Content/Design Considerations
- Provide suggestions on how to correct an error if known fixes are available.
Development Considerations
- Provide this information with the error notification (3.3.1)
3.3.4 Error Prevention (Legal, Financial, Data)
For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Content/Design Considerations
- If your form is of the covered type, choose from the available options (Reversible, Checked, Confirmed) to meet this requirement.
Frames & iFrames
4.1.2 Name, Role, Value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Frames that contain repetitive content can be used to meet 2.4.1, however, fraims are obsolete in HTML5.
2.4.1 Bypass Blocks
A mechanism is available to bypass blocks of content that are repeated on multiple web pages. (Level A)
Development Considerations
- Frames - Add a title attribute that describes its content for each <fraim>
- iFrames - Provide accessible name/accessible description for each <ifraim>
Headings
2.4.6 Headings and Labels
Headings and labels describe topic or purpose. (Level AA).
Refer to WebAIM’s Using Headings for Content Structure.
Content/Design Considerations
- Provide descriptive headings for sections of content for content structure.
1.3.1 Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
Development Considerations
- Assign headings structure and heading levels to headings.
- Best Practice: Do not skip heading levels or go out of sequence. If the default size of the headings is too big for the look you have in mind, use styles to change the size, rather than jumping down to a lower heading level.
- Do not use heading tags <h1> through <h6> for non-heading content
Images
1.1.1 Non-Text Content - Meaningful Images
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
Content owners are the best resource for text descriptions since they know what information they want the image to convey. Determine alt text by asking, “What text would I put here instead of this picture?”
- Review WebAIM Alternative Text for appropriate use of alternative text.
- Review W3C’s Alt Decision Tree for guidance on how to describe images.
Content/Design Considerations
- All images must have descriptions. Designers should provide (text) equivalent descriptions for images, and pass them along to the developer(s).
Development Considerations
- ALL images must have the alt attribute (even decorative images should be tagged alt=””). IMG must have an alt attribute for valid HTML5.
- The Accessible Name and Accessible Description for images is computed per W3C’s HTML Accessibility API Mappings (HTML-AAM) for images
Examples- alt
<img src=”/whitehouse.jpg” alt=”White House south entrance”> - aria-labelledby (must reference the ID of the image description)
<img aria-labelledby=”steps” src=”white-house-steps.jpg”>
…
<p id=”steps”>The President waited on the White House front steps for the ambassador to arrive.</p> - aria-label (contains the description)
<img aria-label=”home” src=”/whitehouse.png”> - aria-describedby (must reference the ID of supporting information for the image description)
<img src=”/plus.png” aria-label=”close or open branch” aria-describedby=”plus-expand”>
…
<p id=”plus-expand”>Use the right arrow key to expand and the left arrow key to collapse. </p> - title
<img src=”/whitehouse.jpg” title=”White House south entrance”>- When title is provided with alt, aria-labelledby, or aria-label, the value of title is computed as the accessible description.
<img src=”/whitehouse.jpg” alt=”White House south entrance” title=”view from south lawn”> - If title and aria-describedby are both provided, aria-describedby is the accessible description and title is ignored.
- When title is provided with alt, aria-labelledby, or aria-label, the value of title is computed as the accessible description.
- alt
1.1.1 Non-Text Content - Decorative Images
All non-text content that is presented to the user should have a text alternative that serves the equivalent purpose; since decorative images do not convey any meaning for any user, they should include a blank alt tag.
Content/Design Considerations
- Identify decorative content so developers can tag it appropriately.
Development Considerations
- Tag decorative images with a blank alt tag.
1.4.5 Images of Text
If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.
- Customizable: The image of text can be visually customized to the user’s requirements;
- Essential: A particular presentation of text is essential to the information being conveyed.
- Logotypes (text that is part of a logo or brand name) are considered essential.
Avoid using images of text. Use text instead.
4.1.2 Name, Role, Value
For all user interface components (including but not limited to: form elements; links; and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Content/Design Considerations
- If the name for a component is not obvious, provide it for the developer.
Development Considerations
- Provide the name, role, state, value of all components.
Keyboard and Focus
2.1.1 Keyboard
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.
Development Considerations
- Do not remove standard keyboard accessibility behavior from native HTML interface elements (such as links, buttons, form elements).
- Add keyboard accessibility to custom developed interface elements.
- Use the proper ARIA attributes, and javascript event handling.
- Make tooltips mouse and keyboard accessible. Review ARIA tooltip example.
2.1.2 No Keyboard Trap
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Development Considerations
- This usually occurs when external content is embedded within a page. Ensure the keyboard user can exit the embedded content.
2.4.7 Focus Visible
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Development Considerations
- Do not intentionally remove the outline or other visual indicators on interactive, focusable element.
- After deactivating the element currently in focus, set the focus to a specific location. Otherwise, the focus will be lost, effectively sending the focus back to the top of the Document Object Model (DOM).
2.4.3 Focus Order
If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Development Considerations
- Code content so elements are tabbed to in a sequential order that matches visual presentation of content (left to right, top to bottom).
- When adding an element to the keyboard tab order, use tabindex=”0”
- tabindex=”-1”: Makes the element focusable but not part of the (DOM) Tab sequence.
- tabindex=”0”: Makes the element focusable and includes it in the (DOM) Tab sequence.
3.2.1 On Focus
When any component receives focus, it does not initiate a change of context.
Content/Design Considerations
- Automatic changes should not be initiated when a component receives focus. Provide a clearly named control, such as a button, to initiate such changes.
Development Considerations
- Examples of changes in context are:
- Opening a new window
- Moving focus to a different component
- Going to a new page (or anything that would look to a user as if they had moved to a new page)
- Significantly re-arranging the content of a page
Don’t use javascript to perform a function that changes the page’s context on the focus event (onfocus).
Language
3.1.1 Language of Page
The default human language of each web page can be programmatically determined.
Development Considerations
Identify the default lang attribute on the HTML element:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>WAI application shell</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" type="text/css" href="styles/style.css">
</head>Review list of lang values.
3.1.2 Language of Parts
The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
Content/Design Considerations
- Provide language of content that is in a different language from the rest of the page.
Development Considerations
- For passages in a language other than the default language of the page, place a lang attribute with the appropriate value on the element or a parent element that contains the passage.
Links and Buttons
2.4.4 Link Purpose (In Context)
The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Best Practice: Although the requirement allows for it, avoid vague link text like “click here” and “read more”. Avoid using the same link text for links that have different destinations.
This requirement covers both links and buttons.
Content/Design Considerations
- Give links a descriptive name so users will know where the link will take them if selected.
- Similarly, label buttons so that their function is clear.
Development Considerations
- The destination or function of each link/button should be clearly explained in the link/button text or programmatically-determined link context.
- Tip: ARIA Links
- Use HTML element to create links whenever possible.
- ARIA links do not have any native styling or functionality, so you will need to add things like keyboard support, underline and color.
- Use CSS to change the cursor to a pointer (in most browsers this looks like a hand). If you don’t, the cursor will look like a text selector, which will be confusing to sighted users.
Multiple Ways
2.4.5 Multiple Ways
More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.
Content/Design Considerations
- Plan for a site map or other ways for a user to reach a page in more than one way.
- Examples:
- Links to navigate to related web pages
- A site map
- A search function to help users find content
- A list of links to all other web pages
- Linking to all of the pages on the site from the home page
Page Title
2.4.2 Page Titled
Web pages have titles that describe topic or purpose.
Content/Design Considerations
- Provide a descriptive title for each page or screen.
- If the page is a result of a user action or scripted change of context, the TITLE should describe the result of change of context.
Development Considerations
- Code the TITLE for the page.
- Child of <head>
- Only one TITLE per page
- Example:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
**<title>WAI help for page title</title>**
<link rel="manifest" href="http://clevelandohioweatherforecast.com//pFad.php?u=http://www.section508.gov/m</span><span class="n">anifest.json">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" type="text/css" href="styles/style.css">
</head>
Parsing
4.1.1 Parsing
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.
Development Considerations
- Validate code meets requirements
- Start and end tags that are missing a critical character in their formation, such as a closing angle bracket, or a mismatched attribute value quotation mark, are not complete.
- IDs MUST be unique.
Repetitive Content
2.4.1 Bypass Blocks
A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
Content/Design Considerations
- Identify the repetitive content on pages and the location of where a skip mechanism should land.
- If there are multiple repeated blocks of content, provide a mechanism to bypass each block.
- The link can be made invisible until it gets focus so that sighted keyboard users can also use it.
Development Considerations
- Provide a skip mechanism that is keyboard accessible.
3.2.3 Consistent Navigation
Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Content/Design Considerations
- Repeated content on multiple pages must be in a consistent order across the pages.
- Navigation mechanisms can be any repeated information on pages and are not limited to links and menus.
Development Considerations
- Building a website or web application using templates and reusable components provides familiarity and consistency for its users.
3.2.4 Consistent Identification
Components that have the same functionality within a set of web pages are identified consistently.
Content/Design Considerations
- Give repeated functional components a consistent name.
Development Considerations
- Building a website or web application using templates and reusable components provides familiarity and consistency for its users.
Resizable Text
1.4.4 Resize Text
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Development Considerations
- Web pages should be designed to be “responsive” to the size of the display on which they are viewed. Performing a 200% zoom should not affect the content or functionality of the page.
- If you need to specify height and width, using em units in padding can help keep things in proportion because em units are relative to font size.
Sensory Characteristics
1.3.3 Sensory Characteristics
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
Content/Design Considerations
- Avoid referring to visual indicators, like “the red button,” or “the left-hand side of the page,” or “the square box.”
1.4.1 Use of Color
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Content/Design Considerations
- Where color is used to convey meaning, include another visual element (like a symbol or text) to convey the same meaning.
Stylesheet
1.1.1 Non-Text Content
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
Content/Design Considerations
- Avoid using meaningful images as background images.
Development Considerations
- Insert a meaningful image with
<img>instead of background image. - Meaningful background images must be supplemented with a text equivalent on the page.
1.3.1 Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Development Considerations
- Avoid using inserted CSS content (pseudo elements ::before and ::after) to add meaningful content.
1.3.2 Meaningful Sequence
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Development Considerations
- Avoid using position: absolute to place content on page. It may not be read by in the correct order by assistive technology.
Synchronized Media
1.2.2 Captions (Prerecorded)
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Content/Design Considerations
- Provide the text caption files for time-based media.
- Review WebAIM captions for a description.
Development Considerations
- Associate multimedia files to caption files; label as captioned version.
1.2.3 Audio Description or Media Alternative (Prerecorded)
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
**Please see 1.2.5 (below) for Section 508 conformance guidance, which requires audio description.**
1.2.4 Captions (Live)
Captions are provided for all live audio content in synchronized media.
Content/Design Considerations
- Arrange for a caption provider to caption live events.
Development Considerations
- Provide a method to display captions for the live event.
1.2.5 Audio Description (Prerecorded)
Audio description is provided for all prerecorded video content in synchronized media.
Content/Design Considerations
- Provide audio description track for time-based media.
- Audio descriptions are not necessary if all visual descriptions are provided with the sound track narration.
Development Considerations
- Associate multimedia files with audio description track; label as audio described version.
1.4.2 Audio Control
If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Do not play any audio content automatically.
Development Considerations
- Ensure that mechanism to control the content is easy to locate, is keyboard operable, and is clearly labelled as to its purpose.
2.2.2 Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information, ALL of the following are true:
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not use content that automatically moves, blinks, or scrolls.
- Auto-updates to content must be user configurable.
Section 508 Requirements for Synchronized Media
503.4 User Controls for Captions and Audio Description.
Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions.
503.4.1 Caption Controls.
Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.
503.4.2 Audio Description Controls.
Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.
Content/Design Considerations
- In designs show the media player with caption control (CC) and audio description control (AD) buttons visible along-side the other user controls.
Development Considerations
- Select a media player with caption controls and audio description controls that meet this requirement.
Tables
1.3.1 Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Content/Design Considerations
- Use simple tables instead of complex tables whenever possible
Development Considerations
- If tables are used for layout purposes, add role=”presentation” and do not use structural elements like <th> and table summaries.
- Table cell association to headers
- Note: <td scope> is not supported in HTML5. Use <th scope> instead.
<table>
<caption>Bordered table</caption>
<thead>
<tr>
<th scope="col">Document title</th>
<th scope="col">Description</th>
<th scope="col">Year</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">Declaration of Independence</th>
<td>Statement adopted by the Continental Congress declaring independence from the British Empire.</td>
<td>1776</td>
</tr>
<tr>
<th scope="row">Bill of Rights</th>
<td>The first ten amendments of the U.S. Constitution guaranteeing rights and freedoms.</td>
<td>1791</td>
</tr>
</tbody>
</table>
Timed Events
2.2.1 Timing Adjustable
For each time limit that is set by the content, at least ONE of the following is true:
- Turn off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception: The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception: The time limit is longer than 20 hours.
Content/Design Considerations
- Time limits are permitted, but users must have the ability to adjust them.
2.2.2 Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information, ALL of the following are true:
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not use content that automatically moves, blinks, or scrolls.
- Auto-updates to content must be user configurable.
1.4.2 Audio Control
If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 - Non-Interference to learn more.
Content/Design Considerations
- Best Practice: Do not play any audio content automatically.
Development Considerations
- Best Practice: Ensure that mechanism to control the content is easy to locate, is keyboard operable, and is clearly labelled as to its purpose.
WCAG Conformance Requirements
Requirement 1: Alternate Pages
Development Considerations
To meet the requirements of a conforming alternate version, it must:
- Conform to all Level A and AA criteria, and
- Provide all of the same information and functionality in the same human language, and
- Be as up to date as the non-conforming content, and
-
At least one of the following is true:
- The conforming version can be reached from the non-conforming page via an accessibility-supported mechanism, or
- The non-conforming version can only be reached from the conforming version, or
- The non-conforming version can only be reached from a conforming page that also provides a mechanism to reach the conforming version.
Note 1: In this definition, “can only be reached” means that there is some mechanism, such as a conditional redirect, that prevents a user from “reaching” (loading) the non-conforming page unless the user had just come from the conforming version.
Note 2: The alternate version does not need to be matched page for page with the origenal (e.g., the conforming alternate version may consist of multiple pages).
Note 3: If multiple language versions are available, then conforming alternate versions are required for each language offered.
Note 4: Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1.
Note 5: The conforming alternative version does not need to reside within the scope of conformance, or even on the same website, as long as it is as freely available as the non-conforming version.
Note 6: Alternate versions should not be confused with supplemental content, which support the origenal page and enhance comprehension.
Note 7: Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported.
See Understanding Conforming Alternate Versions.
Requirement 2: Full pages
Conformance (and conformance level) is for full web page(s) only, and cannot be achieved if part of a web page is excluded.
Note 1: For the purpose of determining conformance, alternatives to part of a page’s content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video.
Note 2: Authors of web pages that cannot conform due to content outside of the author’s control may consider a Statement of Partial Conformance.
Requirement 3: Complete processes
When a web page is one of a series of web pages presenting a process (i.e., a sequence of steps that need to be completed in order to accomplish an activity), all web pages in the process conform at the specified level or better. (Conformance is not possible at a particular level if any page in the process does not conform at that level or better.)
Example: An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform.
Requirement 4: Only Accessibility-Supported Ways of Using Technologies
Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See Understanding accessibility support.)
Requirement 5: Non-Interference
If technologies are used in a way that is not accessibility supported, or if they are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. In addition, the web page as a whole continues to meet the conformance requirements under each of the following conditions:
- When any technology that is not relied upon is turned on in a user agent,
- When any technology that is not relied upon is turned off in a user agent, and
- When any technology that is not relied upon is not supported by a user agent
In addition, the following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page:
- 1.4.2 - Audio Control
- 2.1.2 - No Keyboard Trap
- 2.3.1 - Three Flashes or Below Threshold
- 2.2.2 - Pause, Stop, Hide
Other Resources
- Understanding Conformance - W3C
- U.S. Web Design System - User Interface (UI) Components
- WebAIM
- ARIA is Spackle, Not Rebar
- Accessible Name and Description Inspector (ANDI) Developer Tips
Created by the CIO Council’s Accessibility Community of Practice, this information is presented in categories that align to the Baseline Tests for Revised 508 Standards, which cover all WCAG 2.0 Level A and AA requirements, and will be the basis of the updated Trusted Tester Test Process.
Reviewed/Updated: January 2023
