{"id":1187,"date":"2024-07-08T16:36:02","date_gmt":"2024-07-08T16:36:02","guid":{"rendered":"https:\/\/html5accessibility.com\/stuff\/?p=1187"},"modified":"2024-07-18T12:11:41","modified_gmt":"2024-07-18T12:11:41","slug":"wcag-level-a-bang-for-your-app-a11y-buck","status":"publish","type":"post","link":"https:\/\/html5accessibility.com\/stuff\/2024\/07\/08\/wcag-level-a-bang-for-your-app-a11y-buck\/","title":{"rendered":"WCAG (Level A) BANG for your APP A11Y BUCK"},"content":{"rendered":"

\"Protest<\/p>\n

Image source<\/a><\/p>\n

Updated 10 July 2024<\/strong><\/p>\n

Does WCAG 2.2 Level A apply to Native apps?<\/h2>\n

yes, mostly<\/em><\/strong><\/p>\n

How\/where it (non-normatively) applies is detailed in Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)<\/a><\/p>\n

Below is what I think is the pertinent information for Level A criteria in an abbreviated form, which is hopefully useful.<\/p>\n

Also see: Peaky WCAG (Level AA) BANG for your APP A11Y BUCK<\/a><\/p>\n

With added\u00a0APPT<\/a>\u00a0solutions for apps:\u00a0<\/strong>Android, Jetpack Compose, iOS, SwiftUI, Flutter, React Nativ, .NET MAUI, Xamarin:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
WCAG Level A for apps<\/caption>\n
Criteria<\/th>\nApplies<\/th>\nRemarks and Explanations<\/th>\n<\/tr>\n<\/thead>\n
1.1.1 Non-text Content<\/a><\/p>\n

Implementation solutions for 1.1.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.1.1<\/a><\/p>\n

Note 1<\/a><\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

1.2.1 Audio-only and Video-only (Prerecorded)<\/a><\/p>\n

Implementation solutions for 1.2.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.2.1<\/a>.<\/p>\n

Note 1<\/a><\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

1.2.2 Captions (Prerecorded)<\/a><\/p>\n

Implementation solutions for 1.2.2<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.2.2<\/a>.<\/p>\n

Note 1<\/a><\/p>\n

The WCAG 2 definition of \u201ccaptions<\/a>\u201d notes that \u201cin some countries, captions are called subtitles…\u201d<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

1.2.3 Audio Description or Media Alternative (Prerecorded)<\/a><\/p>\n

Implementation solutions for 1.2.3<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.2.3<\/a>.<\/p>\n

Note 1<\/a>:<\/p>\n

The WCAG 2 definition of \u201caudio description<\/a>\u201d says that \u201caudio description\u201d is \u201calso called \u2018video description\u2019 and \u2018descriptive narration\u2019\u201d.<\/p><\/blockquote>\n

Note 2<\/a>:<\/p>\n

Secondary or alternate audio tracks are commonly used for this purpose.<\/p><\/blockquote>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

1.3.1 Info and Relationships<\/a><\/p>\n

Implementation solutions for 1.3.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.3.1<\/a>.<\/p>\n

Note 1<\/a>:<\/p>\n

In software, programmatic determinability is best achieved through the use of\u00a0accessibility services provided by platform software<\/a>\u00a0to enable interoperability between software and assistive technologies and accessibility features of software.<\/p><\/blockquote>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

1.3.2 Meaningful Sequence<\/a><\/p>\n

Implementation solutions for 1.3.2<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.3.2<\/a>.<\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

1.3.3 Sensory Characteristics<\/a><\/p>\n

Implementation solutions for 1.3.3<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.3.3<\/a>.<\/td>\n<\/tr>\n
1.4.1 Use of Color<\/a><\/p>\n

Implementation solutions for 1.4.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.4.1<\/a>.<\/td>\n<\/tr>\n
1.4.2 Audio Control<\/a><\/p>\n

Implementation solutions for 1.4.2<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.4.2<\/a>, replacing \u201con a Web page\u201d with \u201cin a non-web document or software\u201d, \u201cany content\u201d with \u201cany part of a non-web document or software\u201d, \u201cwhole page\u201d with \u201cwhole document or software\u201d, and \u201con the Web page\u201d with \u201cin the document or software\u201d; and removing \u201cSee Conformance Requirement 5: Non-Interference\u201d<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.1.1 Keyboard<\/a><\/p>\n

Implementation solutions for 2.1.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.1.1<\/a>.<\/p>\n

Note 1<\/a>:<\/p>\n

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)…<\/p><\/blockquote>\n

Note 2<\/a>:<\/p>\n

This success criterion does not imply that software always needs to directly support a keyboard or \u201ckeyboard interface\u201d. Nor does it imply that software always needs to provide a\u00a0virtual keyboard<\/a>.<\/p><\/blockquote>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

2.1.2 No Keyboard Trap<\/a><\/p>\n

Implementation solutions for 2.1.2<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.1.2<\/a>, replacing \u201cpage\u201d with \u201cnon-web document or software\u201d and \u201con the Web page\u201d with “in the non-web document or software”; and removing \u201cSee Conformance Requirement 5: Non-Interference\u201d.<\/p><\/blockquote>\n

See also Note 1<\/a>, Note 2, <\/a>\u00a0Note 3<\/a> and\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

2.1.4 Character Key Shortcuts<\/a><\/p>\n

Implementation solutions for 2.1.4<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.1.4<\/a><\/p>\n

Note 1<\/a>:<\/p>\n

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\u00a0keyboard shortcut<\/a>\u00a0definition for more details.<\/p><\/blockquote>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

2.2.1 Timing Adjustable<\/a><\/p>\n

Implementation solutions for 2.2.1<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in Intent from Understanding Success Criterion 2.2.1<\/a>, replacing \u201cthe content\u201d with \u201cnon-web documents or software\u201d.<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.2.2 Pause, Stop, Hide<\/a><\/p>\n

Implementation solutions for 2.2.2<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.2.2<\/a>, replacing \u201cpage\u201d and \u201cWeb page\u201d with \u201cnon-web documents and software\u201d and removing \u201cSee Conformance Requirement 5: Non-Interference\u201d in Note 2 of the success criterion.<\/p><\/blockquote>\n

See also Note 1<\/a>, Note 2, <\/a>\u00a0Note 3<\/a>, Note 4<\/a> and Note 5<\/a><\/td>\n<\/tr>\n

2.3.1 Three Flashes or Below Threshold<\/a><\/p>\n

Implementation solutions for 2.3.1<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.3.1<\/a>, replacing \u201cWeb pages\u201d with \u201cnon-web documents or software\u201d , \u201cthe whole page\u201d with \u201cthe whole non-web document or software\u201d, and \u201cthe Web page\u201d with \u201cthe non-web document or software\u201d; and removing \u201cSee Conformance Requirement 5: Non-Interference\u201d.<\/p><\/blockquote>\n

See also the Note<\/a><\/td>\n<\/tr>\n

2.4.1 Bypass Blocks<\/a><\/p>\n

Implementation solutions for 2.4.1<\/a><\/td>\n

\"not<\/td>\nThis does not apply within an app<\/strong>, but may<\/em> apply across a set of related<\/em> apps.<\/p>\n

See also Note 1<\/a>, Note 2, <\/a>\u00a0Note 3<\/a>, Note 4<\/a> and Note 5<\/a><\/td>\n<\/tr>\n

2.4.2 Page Titled<\/a><\/p>\n

Implementation solutions for 2.4.2<\/a><\/td>\n

\"not<\/td>\nAppears to apply to whole applications<\/a> rather than individual screens. Although the implementation advice available<\/a> appears to provide individual screen level methods.<\/p>\n

Also see Issue #437<\/a> and Mobile Content Accessibility Guidelines (MCAG) 3.1.1. Screen Titled<\/a><\/td>\n<\/tr>\n

2.4.3 Focus Order<\/a><\/p>\n

Implementation solutions for 2.4.3<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.4.3<\/a>\u00a0replacing \u201ca Web page\u201d with \u201cnon-web documents or software\u201d.<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.4.4 Link Purpose (In Context)<\/a><\/p>\n

Implementation solutions for 2.4.4<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written and as described in\u00a0Intent from Understanding Success Criterion 2.4.4<\/a>.<\/p><\/blockquote>\n

Note<\/a>:<\/p>\n

In software, a \u201clink\u201d 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.)<\/strong><\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.5.1 Pointer Gestures<\/a><\/p>\n

Implementation solutions for 2.5.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.1<\/a><\/p>\n

See also Note 1<\/a>, Note 2<\/a>, Note 3<\/a> and Note 4<\/a><\/td>\n<\/tr>\n

2.5.2 Pointer Cancellation<\/a><\/p>\n

Implementation solutions for 2.5.2<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.2<\/a>, making changes to the notes for non-web documents by replacing \u201cweb content\u201d 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”.<\/p><\/blockquote>\n

See also Note 1<\/a>, Note 2, <\/a>\u00a0Note 3<\/a>, Note 4<\/a>, Note 5<\/a>, Note 6<\/a> and Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

2.5.3 Label in Name<\/a><\/p>\n

Implementation solutions for 2.5.3<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.3<\/a>.<\/td>\n<\/tr>\n
2.5.4 Motion Actuation<\/a><\/p>\n

Implementation solutions for 2.5.4<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.4<\/a>.<\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

3.1.1 Language of Page<\/a><\/p>\n

Implementation solutions for 3.1.1<\/a><\/td>\n

\"yes\"<\/td>\nApplies to application as a whole rather than individual screens<\/strong><\/p>\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.1.1<\/a>\u00a0replacing \u201ceach web page\u201d with \u201cnon-web documents or software\u201d<\/strong>.<\/p>\n

Note 1<\/a>:<\/p>\n

Where software platforms provide a \u201clocale \/ language\u201d setting, applications that use that setting and render their interface in that \u201clocale \/ language\u201d would comply with this success criterion. Applications that do not use the platform \u201clocale \/ language\u201d setting but instead use an\u00a0accessibility-supported<\/a>\u00a0method for exposing the human language of the\u00a0software<\/a>\u00a0would also comply with this success criterion. Applications implemented in technologies where\u00a0assistive technologies<\/a>\u00a0cannot determine the human language and that do not support the platform \u201clocale \/ language\u201d setting may not be able to meet this success criterion in that locale \/ language.<\/p><\/blockquote>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

3.2.1 On Focus<\/a><\/p>\n

Implementation solutions for 3.2.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.2.1<\/a><\/p>\n

See also, the Note<\/a><\/td>\n<\/tr>\n

3.2.2 On Input<\/a><\/p>\n

Implementation solutions for 3.2.2<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.2.2<\/a><\/td>\n<\/tr>\n
3.2.6 Consistent Help<\/a><\/p>\n

Implementation solutions for 3.2.6<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong> and as described in\u00a0Intent from Understanding Success Criterion 3.2.6<\/a>, 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”.<\/p><\/blockquote>\n

See also Note 1<\/a>, Note 2<\/a> and Note 3<\/a><\/td>\n<\/tr>\n

3.3.1 Error Identification<\/a><\/p>\n

Implementation solutions for 3.3.1<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.3.1<\/a><\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n

3.3.2 Labels or Instructions<\/a><\/p>\n

Implementation solutions for 3.3.2<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.3.2<\/a>.<\/td>\n<\/tr>\n
3.3.7 Redundant Entry<\/a><\/p>\n

Implementation solutions for 3.3.7<\/a><\/td>\n

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.3.7<\/a>.<\/td>\n<\/tr>\n
4.1.1 Parsing<\/a><\/td>\nnot applicable<\/td>\n <\/p>\n

2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata<\/a> and the WCAG 2.1 <\/a>Editorial Errata<\/a><\/td>\n<\/tr>\n

4.1.2 Name, Role, Value<\/a><\/p>\n

Implementation solutions for 4.1.2<\/a><\/td>\n

\"yes\"<\/td>\n\n

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 4.1.2<\/a>, replacing the note with: \u201cThis 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.\u201d.<\/p><\/blockquote>\n

See also Note 1<\/a>, Note 2 <\/a>and Note 3<\/a><\/p>\n

See also the\u00a0Comments on Closed Functionality<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Real Surreal<\/h2>\n