This is an Editor's draft, created by the Mobile Accessibility Task Force (MATF) at the W3C.
You can find our working repository at Github.
(Level A)
Placeholder
(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 view – or provided in an alternate version that meets the success criteria.
(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”.
(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.
(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”.
(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.
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(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 view”, “any content” with “any view”, “whole page” with “whole view”, and “on the Web page” with “in the 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 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 view that does not meet this success criterion can interfere with a user's ability to use the whole view, all content in the view (whether it is used to meet other success criteria or not) must meet this success criterion.
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level AA)
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.5.
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.2.1, replacing “the content” with “views”.
With this substitution, it would read:
2.2.1 Timing Adjustable: For each time limit that is set by views, at least one of the following is true:
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.
(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 “view” 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 view, all content on the 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.
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.3.1, replacing “Web pages” with “views”, “the whole page” with “the whole view”, and “the Web page” with “the view”; and removing “See Conformance Requirement 5: Non-Interference”.
With these substitutions, it would read:
2.3.1 Three Flashes or Below Threshold: 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 view, all content on the view (whether it is used to meet other success criteria or not) must meet this success criterion.
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.3.
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.4.
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(Level A)
Placeholder
(Level AA)
Placeholder
(Level AA)
Placeholder
(Level A)
Placeholder
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.1.
(Level A)
Placeholder
(Level AA)
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.3.
(Level AA)
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.4 replacing “web pages” with “views”.
With this substitution, it would read:
3.3.4 Error Prevention (Legal, Financial, Data): For views 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:
(Level A)
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.7.
(Level AA)
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.8, replacing “the Web site” with “a view”.
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
Alternative Another authentication method that does not rely on a cognitive function test.
Mechanism A mechanism is available to assist the user in completing the cognitive function test.
Object Recognition The cognitive function test is to recognize objects.
Personal Content The cognitive function test is to identify non-text content the user provided to a view.
NOTE 1
"Object recognition" and "Personal content" may be represented by images, video, or audio.
NOTE 2
Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing.
NOTE 3
If the non-web software is an application, passwords used to unlock the underlying platform software are out of scope for this requirement as these are not up to a software application’s author.
(Level A)
(Obsolete and removed)
(Level A)
Placeholder
(Level AA)
Placeholder