| 1.1.1 Non-text Content
Implementation solutions for 1.1.1 |
 |
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.1.1
Note 1
See also the Comments on Closed Functionality. |
| 1.2.1 Audio-only and Video-only (Prerecorded)
Implementation solutions for 1.2.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.1.
Note 1
See also the Comments on Closed Functionality. |
| 1.2.2 Captions (Prerecorded)
Implementation solutions for 1.2.2 |
|
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…”
|
| 1.2.3 Audio Description or Media Alternative (Prerecorded)
Implementation solutions for 1.2.3 |
|
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.
See also the Comments on Closed Functionality. |
| 1.3.1 Info and Relationships
Implementation solutions for 1.3.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.1.
Note 1:
In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies and accessibility features of software.
See also the Comments on Closed Functionality. |
| 1.3.2 Meaningful Sequence
Implementation solutions for 1.3.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.2.
See also the Comments on Closed Functionality. |
| 1.3.3 Sensory Characteristics
Implementation solutions for 1.3.3 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.3. |
| 1.4.1 Use of Color
Implementation solutions for 1.4.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.1. |
| 1.4.2 Audio Control
Implementation solutions for 1.4.2 |
|
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 non-web document or software”, “any content” with “any part of a non-web document or software”, “whole page” with “whole document or software”, and “on the Web page” with “in the document or software”; and removing “See Conformance Requirement 5: Non-Interference”
|
| 2.1.1 Keyboard
Implementation solutions for 2.1.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.1.1.
Note 1:
Keyboard interface does not refer to a physical device but to the interface between the software and any keyboard or keyboard substitute (i.e., an interface where the software accepts text or other keystroke input)…
Note 2:
This success criterion does not imply that software always needs to directly support a keyboard or “keyboard interface”. Nor does it imply that software always needs to provide a virtual keyboard.
See also the Comments on Closed Functionality. |
| 2.1.2 No Keyboard Trap
Implementation solutions for 2.1.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.1.2, replacing “page” with “non-web document or software” and “on the Web page” with “in the non-web document or software”; and removing “See Conformance Requirement 5: Non-Interference”.
See also Note 1, Note 2, Note 3 and Comments on Closed Functionality. |
| 2.1.4 Character Key Shortcuts
Implementation solutions for 2.1.4 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.1.4
Note 1:
The WCAG2ICT interpretation is that a long press of a key (2 seconds or more) and other accessibility features provided by the platform do not meet the WCAG definition of a keyboard shortcut. See the keyboard shortcut definition for more details.
See also the Comments on Closed Functionality. |
| 2.2.1 Timing Adjustable
Implementation solutions for 2.2.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.2.1, replacing “the content” with “non-web documents or software”.
|
| 2.2.2 Pause, Stop, Hide
Implementation solutions for 2.2.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.2.2, replacing “page” and “Web page” with “non-web documents and software” and removing “See Conformance Requirement 5: Non-Interference” in Note 2 of the success criterion.
See also Note 1, Note 2, Note 3, Note 4 and Note 5 |
| 2.3.1 Three Flashes or Below Threshold
Implementation solutions for 2.3.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.3.1, replacing “Web pages” with “non-web documents or software” , “the whole page” with “the whole non-web document or software”, and “the Web page” with “the non-web document or software”; and removing “See Conformance Requirement 5: Non-Interference”.
See also the Note |
| 2.4.1 Bypass Blocks
Implementation solutions for 2.4.1 |
 |
This does not apply within an app, but may apply across a set of related apps.
See also Note 1, Note 2, Note 3, Note 4 and Note 5 |
| 2.4.2 Page Titled
Implementation solutions for 2.4.2 |
|
Appears to apply to whole applications rather than individual screens. Although the implementation advice available appears to provide individual screen level methods.
Also see Issue #437 and Mobile Content Accessibility Guidelines (MCAG) 3.1.1. Screen Titled |
| 2.4.3 Focus Order
Implementation solutions for 2.4.3 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.4.3 replacing “a Web page” with “non-web documents or software”.
|
| 2.4.4 Link Purpose (In Context)
Implementation solutions for 2.4.4 |
|
This applies directly as written and as described in Intent from Understanding Success Criterion 2.4.4.
Note:
In software, a “link” is any text string or image in the user interface outside a user interface control that behaves like a hypertext link. This does not include general user interface controls or buttons. (An OK button, for example, would not be a link.)
|
| 2.5.1 Pointer Gestures
Implementation solutions for 2.5.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.1
See also Note 1, Note 2, Note 3 and Note 4 |
| 2.5.2 Pointer Cancellation
Implementation solutions for 2.5.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2, making changes to the notes for non-web documents by replacing “web content” with “content”, for non-web software applications by replacing “web content that interprets” with “user agents and other software applications that interpret” and “user agent” with “underlying platform software”, and for non-web platform software by replacing “web content” with “platform software”.
See also Note 1, Note 2, Note 3, Note 4, Note 5, Note 6 and Comments on Closed Functionality. |
| 2.5.3 Label in Name
Implementation solutions for 2.5.3 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.3. |
| 2.5.4 Motion Actuation
Implementation solutions for 2.5.4 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.4.
See also the Comments on Closed Functionality. |
| 3.1.1 Language of Page
Implementation solutions for 3.1.1 |
|
Applies to application as a whole rather than individual screens
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.1 replacing “each web page” with “non-web documents or software”.
Note 1:
Where software platforms provide a “locale / language” setting, applications that use that setting and render their interface in that “locale / language” would comply with this success criterion. Applications that do not use the platform “locale / language” setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform “locale / language” setting may not be able to meet this success criterion in that locale / language.
See also the Comments on Closed Functionality. |
| 3.2.1 On Focus
Implementation solutions for 3.2.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.2.1
See also, the Note |
| 3.2.2 On Input
Implementation solutions for 3.2.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.2.2 |
| 3.2.6 Consistent Help
Implementation solutions for 3.2.6 |
|
This applies directly as written and as described in Intent from Understanding Success Criterion 3.2.6, replacing “Web page(s)” and “page(s)” with “non-web document(s) or software program(s)”, “set of Web pages” with “set of non-web documents or set of software programs”, “page content” with “content”, “on the page” with “in the non-web document or software”, “page is serialized” with “non-web document or software content is serialized”, “different page” with “different non-web document, software, or Web page”, and “page variation” with “content layout variation”.
See also Note 1, Note 2 and Note 3 |
| 3.3.1 Error Identification
Implementation solutions for 3.3.1 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.1
See also the Comments on Closed Functionality. |
| 3.3.2 Labels or Instructions
Implementation solutions for 3.3.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.2. |
| 3.3.7 Redundant Entry
Implementation solutions for 3.3.7 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.7. |
| 4.1.1 Parsing |
not applicable |
2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata |
| 4.1.2 Name, Role, Value
Implementation solutions for 4.1.2 |
|
This applies directly as written, and as described in Intent from Understanding Success Criterion 4.1.2, replacing the note with: “This success criterion is primarily for software developers who develop or use custom user interface components. For example, standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.”.
See also Note 1, Note 2 and Note 3
See also the Comments on Closed Functionality. |
One reply on “WCAG (Level A) BANG for your APP A11Y BUCK”
[…] ← WCAG (Level A) BANG for your APP A11Y BUCK […]