Applying WCAG 2.2 to Mobile

This is a draft document, created by the Mobile Accessibility Task Force (MATF) at the W3C.

You can find our working repository at Github.

Success Criterion 1.1.1 Non-text Content

(Level A)

Placeholder

Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.1.

NOTE 1

The alternative can be provided directly in the [screen or view] – or provided in an alternate version that meets the success criteria.

Success Criterion 1.2.2 Captions (Prerecorded)

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.2.

NOTE 1

The WCAG 2 definition of “captions” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.

Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.3.

NOTE 1

The WCAG 2 definition of “audio description” says that “audio description” is “also called ‘video description’ and ‘descriptive narration’”.

NOTE 2

Secondary or alternate audio tracks are commonly used for this purpose.

Success Criterion 1.2.4 Captions (Live)

(Level AA)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.4.

NOTE 1

The WCAG 2 definition of “captions” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.

NOTE 2

The WCAG 2 definition of “captions” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.

Success Criterion 1.2.5 Audio Description (Prerecorded)

(Level AA)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.5.

NOTE 1

The WCAG 2 definition of “audio description” says that audio description is “also called ‘video description’ and ‘descriptive narration’”.

NOTE 2

Secondary or alternate audio tracks are commonly used for this purpose.

Success Criterion 1.3.1 Info and Relationships

(Level A)

Placeholder

Success Criterion 1.3.2 Meaningful Sequence

(Level A)

Placeholder

Success Criterion 1.3.3 Sensory Characteristics

(Level A)

Placeholder

Success Criterion 1.3.4 Orientation

(Level AA)

Placeholder

Success Criterion 1.3.5 Identify Input Purpose

(Level AA)

Placeholder

Success Criterion 1.4.1 Use of Color

(Level A)

Placeholder

Success Criterion 1.4.2 Audio Control

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.2, replacing “on a Web page” with “in a screen or view”, “any content” with “any part of a screen or view”, “whole page” with “whole screen or view”, and “on the Web page” with “in the screen or view”; and removing “See Conformance Requirement 5: Non-Interference”.

With these substitutions, it would read:

1.4.2 Audio Control: If any audio [in a screen or view] 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.

NOTE 1

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole [screen or view], all content on the [screen or view] (whether it is used to meet other success criteria or not) must meet this success criterion.

Success Criterion 1.4.3 Contrast (Minimum)

(Level AA)

Placeholder

Success Criterion 1.4.2 Resize Text

(Level AA)

Placeholder

Success Criterion 1.4.5 Images of Text

(Level AA)

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.5.

Success Criterion 1.4.10 Reflow

(Level AA)

Placeholder

Success Criterion 1.4.11 Non-text Contrast

(Level AA)

Placeholder

Success Criterion 1.4.12 Text Spacing

(Level AA)

Placeholder

Success Criterion 1.4.13 Content on Hover or Focus

(Level AA)

Placeholder

Success Criterion 2.1.1 Keyboard

(Level A)

Placeholder

Success Criterion 2.1.2 No Keyboard Trap

(Level A)

Placeholder

Success Criterion 2.1.4 Character Key Shortcuts

(Level A)

Placeholder

Success Criterion 2.2.1 Timing Adjustable

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.2.1, replacing “the content” with “screens or views”.

With this substitution, it would read:

2.2.1 Timing Adjustable: For each time limit that is set by [screens or views], 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.

NOTE 1

This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

Success Criterion 2.2.2 Pause, Stop, Hide

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.2.2, replacing “page” and “Web page” with “screens or views” and removing “See Conformance Requirement 5: Non-Interference” in Note 2 of the success criterion.

With these substitutions, it would read:

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.

NOTE 1

For requirements related to flickering or flashing content, refer to Guideline 2.3.

NOTE 2

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole [screen or view], all content on the [screens or views] (whether it is used to meet other success criteria or not) must meet this success criterion.

NOTE 3

Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

NOTE 4

An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

NOTE 5

While the success criterion uses the term “information”, the WCAG 2 Intent section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.

Success Criterion 2.3.1 Three Flashes or Below Threshold

(Level A)

This applies directly as written, and as described in Intent from Understanding Success Criterion 2.3.1, replacing “Web pages” with “screens or views” , “the whole page” with “the whole screen or view”, and “the Web page” with “the screen or view”; and removing “See Conformance Requirement 5: Non-Interference”.

With these substitutions, it would read:

2.3.1 Three Flashes or Below Threshold: [Screens or views] 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.

NOTE 1

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole [screen or view], all content on the [screen or view] (whether it is used to meet other success criteria or not) must meet this success criterion.

Success Criterion 2.4.1 Bypass Blocks

(Level A)

Placeholder

Success Criterion 2.4.2 Page Titled

(Level A)

Placeholder

Success Criterion 2.4.3 Focus Order

(Level A)

Placeholder

Success Criterion 2.4.4 Link Purpose (In Context)

(Level A)

Placeholder

Success Criterion 2.4.5 Multiple Ways

(Level AA)

Placeholder

Success Criterion 2.4.6 Headings and Labels

(Level AA)

Placeholder

Success Criterion 2.4.7 Focus Visible

(Level AA)

Placeholder

Success Criterion 2.4.11 Focus Not Obscured (Minimum)

(Level AA)

Placeholder

Success Criterion 2.5.1 Pointer Gestures

(Level A)

Placeholder

Success Criterion 2.5.2 Pointer Cancellation

(Level A)

Placeholder

Success Criterion 2.5.3 Label in Name

(Level A)

Placeholder

Success Criterion 2.5.4 Motion Actuation

(Level A)

Placeholder

Success Criterion 2.5.7 Dragging Movements

(Level AA)

Placeholder

Success Criterion 2.5.8 Target Size (Minimum)

(Level AA)

Placeholder

Success Criterion 3.1.1 Language of Page

(Level A)

Placeholder

Success Criterion 3.1.2 Language of Parts

(Level AA)

Placeholder

Success Criterion 3.2.1 On Focus

(Level A)

Placeholder

Success Criterion 3.2.2 On Input

(Level A)

Placeholder

Success Criterion 3.2.3 Consistent Navigation

(Level AA)

Placeholder

Success Criterion 3.2.4 Consistent Identification

(Level AA)

Placeholder

Success Criterion 3.2.6 Consistent Help

(Level A)

Placeholder

Success Criterion 3.3.1 Error Identification

(Level A)

Placeholder

Success Criterion 3.3.2 Labels or Instructions

(Level A)

Placeholder

Success Criterion 3.3.3 Error Suggestion

(Level AA)

Placeholder

Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)

(Level AA)

Placeholder

Success Criterion 3.3.7 Redundant Entry

(Level A)

Placeholder

Success Criterion 3.3.8 Accessible Authentication (Minimum)

(Level AA)

Placeholder

Success Criterion 4.1.1 Parsing

(Level A)

(Obsolete and removed)

Success Criterion 4.1.2 Name, Role, Value

(Level A)

Placeholder

Success Criterion 4.1.3 Status Messages

(Level AA)

Placeholder