Visual Designer
UX Designer
1 PERCEIVABLE
Information and user interface components must be presentable to users in ways they can perceive.
2 OPERABLE
User interface components and navigation must be operable.
3 UNDERSTANDABLE
Information and the operation of user interface must be understandable.
4 ROBUST
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
1.1 TEXT ALTERNATIVES
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.2 TIME-BASED MEDIA
Provide alternatives for time-based media.
1.3 ADAPTABLE
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.4 DISTINGUISHABLE
Make it easier for users to see and hear content including separating foreground from background.
2.1 OPERABLE
User interface components and navigation must be operable.
2.2 ENOUGH TIME
Provide users enough time to read and use content.
2.3 SEIZURES AND PHYSICAL REACTIONS
Do not design content in a way that is known to cause seizures or physical reactions.
2.4 NAVIGABLE
Provide ways to help users navigate, find content, and determine where they are.
2.5 INPUT MODALITIES
Make it easier for users to operate functionality through various inputs beyond keyboard.
3.1 READABLE
Make text content readable and understandable.
3.2 PREDICTABLE
Make Web pages appear and operate in predictable ways.
3.3 INPUT ASSISTANCE
Help users avoid and correct mistakes.
4.1 COMPATIBLE
Maximize compatibility with current and future user agents, including assistive technologies.
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, except for the situations listed below.

  • Controls, Input
    If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)
  • Time-Based Media
    If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
  • Test
    If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory
    If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • CAPTCHA
    If the purpose of non-text content is to confirm that 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.
  • Decoration, Formatting, Invisible
    If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
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.
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.

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.

1.2.4 Captions (Live)

Captions are provided for all live audio content in synchronized media.

1.2.5 Audio Description (Prerecorded)

Audio description is provided for all prerecorded video content in synchronized media.

1.2.6 Sign Language (Prerecorded)

Sign language interpretation is provided for all prerecorded audio content in synchronized media.

1.2.7 Extended Audio Description (Prerecorded)

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.

1.2.8 Media Alternative (Prerecorded)

An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.

1.2.9 Audio-only (Live)

An alternative for time-based media that presents equivalent information for live audio-only content is provided.

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

1.3.3 Sensory Characteristics

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

1.3.4 Orientation

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

1.3.5 Identify Input Purpose

The purpose of each input field collecting information about the user can be programmatically determined when:

  • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
  • The content is implemented using technologies with support for identifying the expected meaning for form input data.
1.3.6 Identify Purpose

In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.

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.

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.

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 contrast requirement.
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.

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 except for the following:

  • 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.
1.4.6 Contrast (Enhanced)

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

  • Large Text
    Large-scale text and images of large-scale text have a contrast ratio of at least 4.5: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 contrast requirement.
1.4.7 Low or No Background Audio

For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:

  • No Background
    The audio does not contain background sounds.
  • Turn Off
    The background sounds can be turned off.
  • 20 dB
    The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.
1.4.8 Visual Presentation

For the visual presentation of blocks of text, a mechanism is available to achieve the following:

  • Foreground and background colors can be selected by the user.
  • Width is no more than 80 characters or glyphs (40 if CJK).
  • Text is not justified (aligned to both the left and the right margins).
  • Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
  • Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
1.4.9 Images of Text (No Exception)

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

1.4.10 Reflow

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

  • Vertical scrolling content at a width equivalent to 320 CSS pixels;
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

1.4.11 Non-text Contrast

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

  • User Interface Components
    Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
  • Graphical Objects
    Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
1.4.12 Text Spacing

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.

Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.

1.4.13 Content on Hover or Focus

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

  • Dismissable
    A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
  • Hoverable
    If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
  • Persistent
    The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.

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.

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.

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.
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.
2.2.3 No Timing

Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.

2.2.4 Interruptions

Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

2.2.5 Re-authenticating

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.

2.2.6 Timeouts

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

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.

2.3.2 Three Flashes

Web pages do not contain anything that flashes more than three times in any one second period.

2.3.3 Animation from Interactions

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.

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.

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.

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.

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

2.4.8 Location

Information about the user's location within a set of Web pages is available.

2.4.9 Link Purpose (Link Only)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

2.4.10 Section Headings

Section headings are used to organize the content.

2.5.1 Pointer Gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

2.5.2 Pointer Cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event
    The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo
    Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal
    The up-event reverses any outcome of the preceding down-event;
  • Essential
    Completing the function on the down-event is essential.
2.5.3 Label in Name

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

2.5.4 Motion Actuation

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:

  • Supported Interface
    The motion is used to operate functionality through an accessibility supported interface;
  • Essential
    The motion is essential for the function and doing so would invalidate the activity.
2.5.5 Target Size

The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:

  • Equivalent
    The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
  • Inline
    The target is in a sentence or block of text;
  • User Agent Control
    The size of the target is determined by the user agent and is not modified by the author;
  • Essential
    A particular presentation of the target is essential to the information being conveyed.
2.5.6 Concurrent Input Mechanisms

Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.

3.1.1 Language of Page

The default human language of each Web page can be programmatically determined.

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.

3.1.3 Unusual Words

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

3.1.4 Abbreviations

A mechanism for identifying the expanded form or meaning of abbreviations is available.

3.1.5 Reading Level

When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.

3.1.6 Pronunciation

A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

3.2.1 On Focus

When any user interface component receives focus, it does not initiate a change of context.

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.

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.

3.2.4 Consistent Identification

Components that have the same functionality within a set of Web pages are identified consistently.

3.2.5 Change on Request

Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

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.

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

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 security or purpose of the content.

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.
3.3.5 Help

Context-sensitive help is available.

3.3.6 Error Prevention (All)

For Web pages that require the user to submit information, 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.
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.

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.
4.1.3 Status Messages

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Understanding

Let’s imagine a bar chart compares how many widgets were sold in June, July, and August. The short label says, "Figure one - Sales in June, July and August." The longer description identifies the type of chart, provides a high-level summary of the data, trends and implications comparable to those available from the chart. Where possible and practical, the actual data is provided in a table.

Example-4.1-EN.svg
How to Meet

A

  • Identify and annotate decorative images
  • If a meaningful image can be easily described, provide the text alternative
  • When an image is a control, ensure the alternative describes the purpose, not the image
  • Provide succinct descriptions of complex visuals, then offer more detailed information

AA

  • Provide a short name for icons that lack text labels
  • Give videos a title or brief descriptions

AAA

  • Use figure captions to enhance alternative text

A

  • Give decorative images an ALT attribute with an empty string (alt="")
  • Use HTML, ARIA, or technology-specific techniques to add short text alternatives
  • Where relevant text exists in the UI, use arai-labelledby and aria-describedby to reference
  • Provide an accessible method for exposing long text alternatives
  • Unit test: Developers should use verification tools

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play

Screen reader

  • Verify ALTs, labelling, and foreign phrases
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.1 Audio-only and Video-only (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.1 Audio-only and Video-only (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

AAA

  • Consider incorporating a description of meaningful visual content into the audio track or transcript
  • Consider providing a transcript of all spoken content

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

    Manual

  • Check component keyboard interaction
Understanding
How to Meet

A

  • Provide captions for spoken content in videos

AA

  • Ensure captions are accurate, consumable, and complete

A

  • Embed multimedia content that supports closed captions

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.3 Audio Description or Media Alternative (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.3 Audio Description or Media Alternative (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

A

  • Consider incorporating a description of meaningful visual content into the audio track or transcript

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
How to Meet

A

  • Provide captions for spoken content in videos

AA

  • Ensure captions are accurate, consumable, and complete

A

  • Embed multimedia content that supports closed captions

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.5 Audio Description (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.5 Audio Description (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

AAA

  • Describe meaningful visual content in videos

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.6 Sign Language (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.6 Sign Language (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.7 Extended Audio Description (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.7 Extended Audio Description (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.2.8 Media Alternative (Prerecorded) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.2.8 Media Alternative (Prerecorded) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet
Understanding
How to Meet
Understanding
How to Meet

A

  • Provide captions for spoken content in videos

AA

  • Ensure captions are accurate, consumable, and complete

A

  • Embed multimedia content that supports closed captions

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
How to Meet

AAA

  • Flag any content that has a meaningful order

AAA

    - Order content appropriately in the Document Object Model
  • Only use CSS to alter text position without altering meaning

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Screen reader

  • Check meaningful sequence
Understanding
How to Meet

AA

  • Do not rely on senses in instructions

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for foreign and sensory words
Understanding
How to Meet

AA

  • Provide layouts for both landscape and portrait orientations

Manual

  • Check motion operation
Understanding
How to Meet

AAA

  • Flag any inputs that match the common list

AAA

  • Use HTML autocomplete attributes, where appropriate

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Error handling and instructions
Understanding
How to Meet
Understanding
How to Meet

AA

  • Ensure legends do not rely only on the non-contrasting colors to match data points to legend text
  • Confirm color alone does not indicate status or errors

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check use of color, contrast, and images of text
  • Error handling and instructions
Understanding
How to Meet

AA

  • Stop auto-playing content when it receives focus or provide a simple pause mechanism
  • Avoid automatically playing content that lasts more than five seconds
  • Provide an ability to pause, stop or hide auto-playing content

AA

  • Follow core considerations in reducing effort by understanding what you get from design

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing and auto-play
  • Check component keyboard interaction

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet

A

  • Choose text that sufficiently contrast with its background
  • Achieve minimum contrast for all text placed over images or gradient backgrounds

AA

  • Use caution when using placeholders

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check use of color, contrast, and images of text
  • Check pointer hover
  • Check pointer operation
  • Check focus indicator
Understanding
How to Meet

A

  • Unit test: Check that the content can be zoomed

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Resize and re-space text
Understanding
-
How to Meet

AA

  • Do not use images of text when text can be used
  • Provide text alternatives for logos and other essential images of text

Manual

  • Check use of color, contrast, and images of text

Screen reader

  • Verify ALTs, labelling, and foreign phrases
Understanding
How to Meet
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.4.7 Low or No Background Audio for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.4.7 Low or No Background Audio for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet
Understanding
How to Meet
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.4.9 Images of Text (No Exception) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.4.9 Images of Text (No Exception) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet
Understanding
How to Meet

A

  • Reflow content without horizontal scrolling
  • Where responsive design is not supported, provide an option to display content at 256 CSS pixels wide

Manual

  • Reflow text
Understanding
How to Meet

A

  • Confirm input fields are discernable
  • Contrast components against background
  • Ensure visual states for components have sufficient contrast
  • Contrast focus and non-focus states at least 3:1
  • Confirm icon shapes have enough contrast
  • For charts, ensure all data representations achieve 3:1 contrast

AA

  • Ensure overlays and tooltips are visually distinct from other content

Manual

  • Check use of color, contrast, and images of text
  • Check pointer hover
  • Validate pointer operations
Understanding
How to Meet

AAA

  • Create layouts that support the moderate expansion of text

Manual

  • resize and re-space text
Understanding

A button's tooltip is displayed directly below it on mouse hover which can easily be obscured by a large pointer. The tooltip itself is able to be hovered so the mouse pointer can be moved down to its bottom edge in order to view the tooltip text.

Example-3.1-EN.svg
  • Web Content Accessibility Guidelines 2.1
    Refer to 1.4.13 Content on Hover or Focus for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 1.4.13 Content on Hover or Focus for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

AA

  • Where possible, have dynamic content appear when users click, not when they hover
  • If content appears on hover, the new material needs to remain visible until dismissed
  • Understand the requirements for dismissing content that appears on hover

AA

  • Ensure Esc dismisses new content
  • If content appears on hover, the new content needs to remain visible until dismissed
  • Moving the pointer away from the trigger should not be the action that dismisses the new content
  • Ensure custom tooltips and similar hover text can be triggered by keyboard
  • Discuss alternatives to hover text
  • Use caution where interactive controls appear in the hover text

Manual

  • Check pointer hover
Understanding
How to Meet

A

  • Note intended keyboard navigation in wireframes
  • Specify the tab order
  • Ensure all mouse-operable components are reachable by keyboard
  • Reduce tabbing by effective grouping of elements
  • Set expectations and note intended keyboard operation in wireframes
  • Choose standard HTML elements, where possible
  • Confirm framework libraries follow keyboard conventions
  • For custom components, match the ARIA authoring practices keyboard guidance
  • Provide instructions in the UI where keyboard operation differs from the norm
  • Provide a keyboard equivalent for drag and drop
  • Where a component has multiple mouse operations, notate the keyboard equivalent
  • Dismiss notices, modals, and overlays with the Esc

AA

  • Ensure functions of media players are keyboard operable
  • Document keyboard and other accessibility considerations

A

  • Where possible, achieve the desired tab order by adjusting the DOM, rather than overriding the tabindex
  • Use standard HTML elements where possible, using CSS to alter appearance not behavior
  • Be familiar with established keyboard conventions
  • Implement keyboard operation for custom elements
  • Follow core considerations in reducing effort
  • Unit test - confirm component keyboard interaction

AA

  • Make custom media player and animation controls keyboard accessible

Supplemental techniques

  • Note for iOS platform: For keyboards connected to iOS devices, Apple has its own set of Tab and arrow keys behaviors as noted in Wireless Keyboard with VoiceOver.

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check tab or navigation order
  • Check component keyboard interaction
  • Check bypass blocks, consistent navigation, and multiple ways
  • Dynamic update triggers and effects

Screen reader

  • Compare keyboard operation and output
  • Confirm content interaction works with the screen reader
Understanding
How to Meet

A

  • Confirm framework libraries follow keyboard conventions
  • For custom components, match the ARIA authoring practices keyboard guidance
  • Where a component has multiple mouse operations, notate the keyboard equivalent
  • Dismiss notices, modals, and overlays with the Esc

AA

  • Ensure functions of media players are keyboard operable

A

  • Implement keyboard operation for custom elements
  • Follow core considerations in reducing effort
  • Unit test - confirm component keyboard interaction

AA

  • Make custom media player and animation controls keyboard accessible

Development techniques

  • iOS hybrid: Apple recommends using the HTML5 audio and video elements for mobile Safari. These elements support playback natively in the browser using the browser’s built-in controls.
    Developers may also create custom media controls for rich interactivity using CSS and JavaScript.
    See Apple’s About HTML5 Audio and Video and iOS-specific considerations for proper implementation.

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check tab or navigation order
  • Check component keyboard interaction
  • Check bypass blocks, consistent navigation, and multiple ways
Understanding
How to Meet

AAA

  • Avoid time limits
  • When time limits are necessary, allow the user to turn off, adjust, or extend the time limit
  • Make the time-limit notifications accessible

A

  • Follow core considerations in reducing effort
  • Unit test - confirm component keyboard interaction

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Time limits

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet

AA

  • Stop auto-playing content when it receives focus or provide a simple pause mechanism
  • Avoid starting animations or video automatically
  • Avoid automatically playing content that lasts for more than five seconds
  • Provide an ability to pause, stop, or hide auto-playing content

A

  • Follow core considerations in reducing effort
  • Unit test - confirm component keyboard interaction

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check for audio, video, flashing, and auto-play
  • Check component keyboard interaction
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 2.3.1 Three Flashes or Below Threshold for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 2.3.1 Three Flashes or Below Threshold for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

A

  • Avoid flashing content
  • Slow the frequency of flashes to under three times in any one second
  • Reduce the size of the flashing content below the general flash and red flash thresholds

A

  • Follow core considerations in reducing effort by understanding what you get from design

Manual

  • Check for audio, video, flashing, and auto-play
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet

AAA

  • Consider links and other mechanisms to bypass blocks of content
  • Designate appropriate regions, especially header, main and footer

A

  • Follow core considerations in reducing effort by understanding what you get from design

AA

  • Consider adding regions and other ARIA roles to distinguish text groupings

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check bypass blocks, consistent navigation, and multiple ways

Screen reader

  • Compare keyboard operation and output
Understanding
How to Meet

AA

  • In a set of pages, give each a unique title
  • List the unique text string first in a concatenated title

A

  • Code the <title> element on every page according to design

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check labeling, link names, and page titles

Screen reader

  • Check page structure, tables, and headings
Understanding
How to Meet

A

  • Specify the tab order
  • Ensure all mouse-operable components are reachable by keyboard
  • Reduce tabbing by effective grouping of elements
  • Choose standard HTML elements, where possible
  • Where a component has multiple mouse operations, notate the keyboard equivalent

A

  • Ensure interactive elements are reachable with the keyboard
  • Where possible, achieve the desired tab order by adjusting the DOM, rather than overriding the tabindex

Manual

  • Check tab or navigation order
  • Maintaining user's point of regard
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 2.4.4 Link Purpose (In Context) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 2.4.4 Link Purpose (In Context) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

AA

  • Compose stand-alone link text where possible
  • Contextualize generic links such as "Read more"

A

  • Follow core considerations in reducing effort by understanding what you get from design

AA

  • Use ARIA labelling and describing attributes to add additional context to generic link names

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check labeling, link names, and page titles

Screen reader

  • Verify ALTs, labelling, and foreign phrases
Understanding
How to Meet

AAA

  • Use tables of content and site maps, where appropriate
  • Provide a search function or other features to improve navigation and findability

A

  • Follow core considerations in reducing effort by understanding what you get from design

Manual

  • Check bypass blocks, consistent navigation, and multiple ways
Understanding
How to Meet

A

  • Write clear, consistent, and concise labels
  • Accurately describe content with succinct headings

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check labeling, link names, and page titles
  • Read text for clarity; check for foreign and sensory words

Screen reader

  • Verify ALTs, labelling, and foreign phrases
Understanding
How to Meet

A

  • Contrast focus and non-focus states at least 3:1

AA

  • Ensure functions of media players are keyboard operable

A

  • When overriding the default focus indicator, confirm focus is highly visible
  • Follow core considerations in reducing effort by understanding what you get from design
  • Unit test - confirm component keyboard interaction
  • Unit test - check tab order

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check focus indicator
  • Check tab or navigation order
  • Check component keyboard interaction
  • Check pointer hover
  • Validate pointer operations

Screen reader

  • Compare keyboard operation and output
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet

AA

  • Provide an ability to complete all tasks with clicks, double clicks and other simple pointer actions
  • Don't rely on multipoint gestures like pinch to zoom for custom widgets
  • Don't require swiping or path-based gestures for custom widgets

A

  • Follow core considerations in reducing effort by understanding what you get from design
  • Unit test - confirm component keyboard interaction

Manual

  • Validate pointer operations

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet

AAA

  • Provide a way for users to abort pointer actions
  • Plan ways to reverse or undo pointer actions

A

  • Follow core considerations in reducing effort by understanding what you get from design
  • Unit test - confirm component keyboard interaction

AA

  • Provide accessible ways of cancelling pointer interaction

Manual

  • Validate pointer operations

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet

AA

  • Match the accessible name to the visible label
  • Include the text of the label in the accessible name

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Screen reader

  • Make sure that the visible label text matches the output from the screen reader
Understanding
How to Meet

AA

  • Don't depend on device motion

A

  • Follow core considerations in reducing effort by understanding what you get from design
  • Unit test - confirm component keyboard interaction

Manual

  • Check motion operation

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet

A

  • Set the language of the page

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check the value of the lang attribute reflects the primary language used by the page

Screen reader

  • Foreign language pages are indicated or pronounced properly by the screen reader
Understanding
How to Meet

AAA

  • Notate occurrences of foreign language

AAA

  • Use the lang attribute for foreign words or phrases

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Take note of foreign words used in the text to create a list to check with a screen reader for correct pronunciation.

Screen reader

  • Foreign phrases are indicated or pronounced properly by the screen reader
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet

AAA

  • When any component receives keyboard focus, do not start a content change that can disorient users

AAA

  • Use "activate" rather than "focus" as a trigger
  • Incorporate and run verification tools for unit testing

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Dynamic updates triggers and effects
Understanding
How to Meet

AAA

  • When the setting of any user interface component changes, do not cause unexpected changes elsewhere unless the user is forewarned

AAA

  • Use an onchange event without disorienting the user

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Dynamic updates triggers and effects
Understanding
How to Meet

A

  • Present menus in the same relative order

Manual

  • Check bypass blocks, consistent navigation, and multiple ways
Understanding

An e-commerce application uses a printer icon that allows the user to print receipts and invoices. In one part of the application, the printer icon is labeled "Print receipt" and is used to print receipts, while in another part it is labeled "Print invoice" and is used to print invoices. The labeling is consistent ("Print x"), but the labels are different to reflect the different functions of the icons. Therefore, this example does not fail the Success Criterion.

Example-1.1-EN.svg
  • Web Content Accessibility Guidelines 2.1
    Refer to 3.2.4 Consistent Identification for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 3.2.4 Consistent Identification for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

A

  • Write clear, consistent, and concise labels

Manual

  • Check labeling, link names, and page titles

Screen reader

  • Compare keyboard operation and output
Understanding
How to Meet
Understanding

An airline Web site offers a special promotion on discounted flights. The user is asked to complete a simple form that asks for personal information such as name, address, phone number, seating preference and e-mail address. If any of the fields of the form are either not completed or completed incorrectly, an alert is displayed notifying the user which field or fields were missing or incorrect.

Example-2.1-EN.svg
How to Meet

A

  • Ensure error messages are obvious to everyone
  • Carry out validation in an accessible way
  • Ensure the user can easily get to form elements that need to be fixed
  • Identify and describe errors

AA

  • Distinguish between errors and status messages

A

  • Use accessible methods to implement error messages
  • Implement validation and notification to minimize interruptions

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Error handling and instructions
Understanding
How to Meet

A

  • Provide a label for every input element
  • Consistently locate labels near inputs
  • Persistently display labels
  • Indicate required fields and legends in an accessible manners

AA

  • Consider ways to provide additional context
  • Include instructions when a particular data format is expected
  • Use caution when using placeholders

AAA

  • Designate forms and flag any grouping of inputs

A

  • Programmatically associate inputs with labels

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Manual

  • Check labeling, link names, and page titles
  • Read text for clarity; Check for foreign, and sensory words
  • Error handling and instructions

Screen reader

  • Verify ALTs, labelling, and foreign phrases
  • Confirm content interaction works with the screen reader
Understanding
How to Meet

A

  • Ensure error messages are obvious to everyone
  • Carry out validation in an accessible way
  • Ensure the user can easily get to form elements that need to be fixed
  • Suggest corrections, with enough context for a non-sighted user

A

  • Use accessible methods to implement error messages
  • Implement validation and notification to minimize interruptions

Manual

  • If they are known, suggestions for correction are provided
  • Instructions are provided for specific formatting or values
Understanding
  • Web Content Accessibility Guidelines 2.1
    Refer to 3.3.4 Error Prevention (Legal, Financial, Data) for more information on exceptions, intent, benefits, and techniques.
  • IBM Accessibility Requirements
    Refer to 3.3.4 Error Prevention (Legal, Financial, Data) for more information on accessibility requirements that need to be met for recent releases of several standards and regulations.
How to Meet

A

  • Summarize pending transactions so that users can check and confirm
  • Provide clear instructions when the user can reverse an action

A

  • Unit test - confirm component keyboard interaction

Manual

  • Users have a chance to check, confirm, or reverse actions
Understanding
How to Meet
Understanding
How to Meet
Understanding
How to Meet

Automated

  • Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement

Screen reader

  • Confirm content interaction works with the screen reader
Understanding
How to Meet
Level 1 - No level 1 design tasks for this requirement Level 2 - Consider ways to provide additional context Level 3 - Analyze white space for possible accessibility considerations - Designate appropriate regions, especially header, main and footer Level 1 - Add accessible names for inputs lacking visible labels - If repurposing a standard component, use ARIA to set the correct name and role - On custom components, use ARIA to expose name, role, and value Level 2 - No level 2 developer tasks for this requirement Level 3 - No level 3 developer tasks for this requirement Automated - Test using the IBM Equal Access Accessibility Checker browser extension or integration testing module to identify issues detected for this requirement Manual - No manual checks identify issues specific to this requirement Screen Reader - Display of name, role, value, and state information matches - Dynamic update triggers and effects work with the screen reader
Understanding
How to Meet

AA

  • Determine whether feedback is important enough to disrupt users
  • Mark non-disruptive feedback as status messages, when appropriate
  • Distinguish between errors and status messages
  • Mark non-disruptive feedback as status messages

AA

  • Use role=status to advise on the success or results of an action
  • Use role=alert or an ARIA live region to convey a suggestion or warning

Screen reader

  • Status messages appearing on screen are announced by the screen reader