{"id":1234,"date":"2024-07-09T20:06:33","date_gmt":"2024-07-09T20:06:33","guid":{"rendered":"https:\/\/html5accessibility.com\/stuff\/?p=1234"},"modified":"2024-07-18T12:13:40","modified_gmt":"2024-07-18T12:13:40","slug":"peaky-wcag-level-aa-bang-for-your-app-a11y-buck","status":"publish","type":"post","link":"https:\/\/html5accessibility.com\/stuff\/2024\/07\/09\/peaky-wcag-level-aa-bang-for-your-app-a11y-buck\/","title":{"rendered":"Peaky WCAG (Level AA) BANG for your APP A11Y BUCK"},"content":{"rendered":"

\"Patrick<\/p>\n

Self portrait of Peak WCAG <\/strong>Trash Panda Patrick Lauke<\/a><\/p>\n

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

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

How\/where it (non-normatively) applies is detailed in\u00a0Guidance 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 AA criteria in an abbreviated form, which is hopefully useful.<\/p>\n

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

With added APPT<\/a> solutions for apps: <\/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
WCAG Level AA for apps<\/caption>\n
Criteria<\/th>\nApplies<\/th>\nRemarks and Explanations<\/th>\n<\/tr>\n<\/thead>\n
1.2.4 Captions (Live)<\/a><\/p>\n

Implementation reference for 1.2.4<\/a><\/td>\n

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

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

1.2.5 Audio Description (Prerecorded)<\/a><\/p>\n

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

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

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

1.3.4 Orientation<\/a><\/p>\n

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

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

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

Content that is only used on hardware with a fixed display orientation or that has no sensor to detect or change the orientation is covered under the essential exception and does not need to provide support for orientation changes.<\/p><\/blockquote>\n

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

1.3.5 Identify Input Purpose<\/a><\/p>\n

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

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

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

Non-web software<\/a>\u00a0and\u00a0non-web document<\/a>\u00a0technologies that do not provide attributes that support identifying the expected meaning for the form input data are not in scope for this success criterion.<\/p><\/blockquote>\n

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

For non-web software and non-web documents that present input fields, the terms for the input purposes would be the equivalent terms to those listed in the WCAG 2 section\u00a0Input Purposes for User Interface Components<\/a>\u00a0that are supported by the technology used.<\/p><\/blockquote>\n

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

1.4.3 Contrast (Minimum)<\/a><\/p>\n

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

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

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

1.4.4 Resize text<\/a><\/p>\n

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

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

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

The Intent section refers to the ability to allow users to enlarge the text on screen at least up to 200% without needing to use\u00a0assistive technologies<\/a>. This means that the application provides some means for enlarging the text 200% (zoom or otherwise) without loss of\u00a0content<\/a>\u00a0or functionality, or that the application works with the platform accessibility features to meet this success criterion.<\/p><\/blockquote>\n

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

For non-web software, there may be cases where the platform does not scale all text up to 200%. In such cases, authors are encouraged to meet user needs by scaling text to the extent supported by user settings in the platform.<\/p><\/blockquote>\n

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

1.4.5 Images of Text<\/a><\/p>\n

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

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

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

1.4.10 Reflow<\/a><\/p>\n

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

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.4.10<\/a>, replacing \u201cweb content\u201d with \u201ccontent\u201d.<\/p>\n

Editors Note:<\/p>\n

The WCAG2ICT Task Force made changes to give additional guidance around how 1.4.10 Reflow should be applied to non-web software in response to public comments.<\/span><\/p><\/blockquote>\n

Refer directly to the WCAG2ICT documentation: Applying SC 1.4.10 Reflow to Non-Web Documents and Software<\/a><\/td>\n<\/tr>\n

1.4.11 Non-text Contrast<\/a><\/p>\n

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

\"yes\"<\/td>\nThis applies directly as written<\/strong> and as described in\u00a0Intent from Understanding Success Criterion 1.4.11<\/a>, replacing “user agent” with “user agent or platform software.<\/p>\n

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

An example of appearance modification by the author is content that sets the visual style of a control, such as a color or border, to differ from the default style for the user agent or platform.<\/p><\/blockquote>\n

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

1.4.12 Text Spacing<\/a><\/p>\n

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

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

See also, Note 1<\/a>:<\/p>\n

This success criterion only applies to\u00a0non-web documents<\/a>\u00a0and\u00a0software<\/a>\u00a0that are implemented using markup languages<\/strong> and allow the user to modify these text spacing properties.<\/p><\/blockquote>\n

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

“Content implemented using markup languages” includes parts of software that use markup internally to define a user interface. Examples of markup languages that are used internally to define a software user interface include but are not limited to: HTML (e.g., in\u00a0Electron<\/a>\u00a0applications or iOS application Web views), XAML, XML (e.g., in Android application layouts), and XUL.<\/p><\/blockquote>\n

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

There are several mechanisms that allow users to modify text spacing properties of content implemented in markup languages. For example, an eBook technology may have an available user agent that allows users to override document text styles, or a software application may provide a “user style sheet” facility to modify the appearance of the software’s own user interface. This success criterion does not mean that documents and software need to implement their own mechanisms to allow users to set text spacing; however, when such a mechanism is available, the success criterion requires that content respond appropriately to it.<\/p><\/blockquote>\n

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

1.4.13 Content on Hover or Focus<\/a><\/p>\n

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

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

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 1.4.13<\/a>, replacing “user agent” with “user agent or platform software”, “browser tooltips” with “tooltips”, and “the HTML title attribute” with “user interface object attributes”.<\/p><\/blockquote>\n

See also, Note 1<\/a>:<\/p>\n

Examples of additional content controlled by the\u00a0[user agent or platform software]<\/ins>\u00a0include\u00a0[tooltips]<\/ins>\u00a0created through use of\u00a0[user interface object attributes]<\/ins>.<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.4.5 Multiple Ways<\/a><\/td>\n\"not<\/td>\nThis applies directly as written<\/strong> and described in\u00a0Intent from Understanding Success Criterion 2.4.5<\/a>, replacing \u201cset of Web pages\u201d with \u201cset of non-web documents\u201d and \u201cset of software programs\u201d.<\/strong><\/p>\n

See also, Note 1<\/a>:<\/p>\n

See\u00a0set of documents<\/a>\u00a0and\u00a0set of software programs<\/a>\u00a0in the Key Terms section of the Introduction to determine when a group of documents or software is considered a set for this success criterion. (Sets of software that meet this definition appear to be extremely rare.) Those implementing this document (WCAG2ICT) will need to consider if this success criterion is appropriate to apply to non-web documents and software. See the\u00a0Interpretation of Web Terminology in a Non-web Context<\/a>.<\/p><\/blockquote>\n

, Note 2<\/a>, Note 3<\/a>, Note 4<\/a>, Note 5<\/a><\/p>\n

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

2.4.6 Headings and Labels<\/a><\/p>\n

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

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

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

In\u00a0software<\/a>, headings and labels are used to describe sections of content<\/a>\u00a0and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

2.4.7 Focus Visible<\/a><\/p>\n

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

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

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

2.4.11 Focus Not Obscured (Minimum)<\/a><\/p>\n

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

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

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

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

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.7<\/a>, replacing “user agent” with “user agent or platform software”, and 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>, and Note 4<\/a><\/td>\n<\/tr>\n

2.5.8 Target Size (Minimum)<\/a><\/p>\n

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

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

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 2.5.8<\/a>, replacing “user agent” with “user agent or platform software” and “on the same page” with “in the same non-web document or software”.<\/p><\/blockquote>\n

See also, Note 1<\/a>:<\/p>\n

Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders with granular values, color pickers displaying a gradient of colors, or editable areas where you position the cursor.<\/p><\/blockquote>\n

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

For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.<\/p><\/blockquote>\n

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

In technologies where CSS is not used, the definition of ‘CSS pixel’ applies as described in\u00a0Applying \u201cCSS pixel\u201d to Non-Web Documents and Software<\/a>.<\/p><\/blockquote>\n<\/td>\n<\/tr>\n

3.1.2 Language of Parts<\/a><\/p>\n

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

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.1.2<\/a>\u00a0replacing \u201ccontent\u201d with \u201cnon-web document or software\u201d.<\/p>\n

See also, Note 1<\/a>:<\/p>\n

There are some\u00a0software<\/a>\u00a0and\u00a0non-web document<\/a>\u00a0technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the non-web document or software, and it would not be possible to meet this success criterion with those technologies.<\/p><\/blockquote>\n

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

3.2.3 Consistent Navigation<\/a><\/td>\n\"not<\/td>\n\n

This applies directly as written<\/strong> and described in\u00a0Intent from Understanding Success Criterion 3.2.3<\/a>, replacing \u201cset of Web pages\u201d with \u201cset of non-web documents\u201d and \u201cset of software programs\u201d.<\/p><\/blockquote>\n

See also, Note 1<\/a>:<\/p>\n

See\u00a0set of documents<\/a>\u00a0and\u00a0set of software programs<\/a>\u00a0in the Key Terms section of the Introduction to determine when a group of documents or software programs is considered a set for this success criterion. (Sets of software that meet this definition appear to be extremely rare.) Those implementing this document (WCAG2ICT) will need to consider if this success criterion is appropriate to apply to non-web documents and software. See the\u00a0Interpretation of Web Terminology in a Non-web Context<\/a>.<\/p><\/blockquote>\n

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

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

3.2.4 Consistent Identification<\/a><\/td>\n\"not<\/td>\n\n

This applies directly as written<\/strong> and described in\u00a0Intent from Understanding Success Criterion 3.2.4<\/a>, replacing \u201cset of web pages\u201d with \u201cset of non-web documents\u201d and \u201cset of software programs\u201d.<\/p><\/blockquote>\n

See also, Note 1<\/a>:<\/p>\n

See\u00a0set of documents<\/a>\u00a0and\u00a0set of software programs<\/a>\u00a0in the Key Terms section of the Introduction to determine when a group of documents or software programs is considered a set for this success criterion. (Sets of software that meet this definition appear to be extremely rare.) Those implementing this document (WCAG2ICT) will need to consider if this success criterion is appropriate to apply to non-web documents and software. See the\u00a0Interpretation of Web Terminology in a Non-web Context<\/a>.<\/p><\/blockquote>\n

and Note 2<\/a><\/td>\n<\/tr>\n

3.3.3 Error Suggestion<\/a><\/p>\n

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

\"yes\"<\/td>\nThis applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.3.3<\/a>.<\/td>\n<\/tr>\n
3.3.4 Error Prevention (Legal, Financial, Data)<\/a><\/p>\n

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

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

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

3.3.8 Accessible Authentication (Minimum)<\/a><\/p>\n

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

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

This applies directly as written<\/strong>, and as described in\u00a0Intent from Understanding Success Criterion 3.3.8<\/a>, \u201cthe Web site\u201d with \u201ca Web site, non-web document, or software\u201d.<\/p><\/blockquote>\n

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

“Object recognition” and “Personal content” may be represented by images, video, or audio.<\/p><\/blockquote>\n

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

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

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

If the non-web software is an application, passwords used to unlock the underlying\u00a0platform software<\/a>\u00a0are out of scope for this requirement as these are not up to a software application\u2019s author.<\/p><\/blockquote>\n

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

There are cases where non-web software has an authentication process and no alternative or assistance mechanism is feasible, for example when entering a password on when starting, powering on \/ turning on an ICT (device or otherwise). In such situations, it may not be possible for the non-web software to meet this success criterion.<\/p><\/blockquote>\n

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

4.1.3 Status Messages<\/a><\/p>\n

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

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

Red Right Hand<\/h2>\n