OVERVIEW and SUMMARY of all AAA SC

[GreggVan]

AAA Overview and Reference Page

Link to all AAA ISSUES

GreggVan 2022 AAA SC Review

In 2022 when we first were setting up WCAG2ICT and deciding whether or not to include AAA provisions, I did a quick review of all of the AAA provisions to see if it was a reasonable amount of work.

My Preliminary Results

ALL AAA provisions apply as written, and as described in Understanding WCAG 2.2 except 3 of them:

2.4.8 Location

replacing “within a set of Web pages” with “in a set of non-web documents or software”.

2.5.6 Concurrent Input Mechanisms

replacing “Web content” with “non-web content or software”.
[Note: MJ suggests just changing web content to content instead (which I agree with) ]

3.3.6 Error Prevention (All)

replacing “Web pages” with “non-web documents or software”.

HOWEVER these are preliminary BEFORE we did any of the other discussions so should be treated as such. We are now ready for the full group to review. For this purpose, the AAA SC have all been given their own ISSUE for review comments.

• Here is a link to the original 2022 word doc with the full review all in one piece if this is easier for review
  • this also includes the UNDERSTANDING document for each success criterion - which is helpful

Summary of AAA Issues Opened in GitHub

Below are the links to the issues for each AAA SC individually where MJ has proposed a resolution for each.

Mary Jo asks that we review each to see if:

1. we agree (if so - leave a thumbs up) or if we think it needs work (if so - leave an eyes symbol because we need to look at it further)
2. consider whether any notes should be added (if so, provide suggested language), and
3. consider closed functionality - Is anything needed in the SC Problematic for Closed Functionality?

Gregg sorted all of the AAA SC by the currently suggested resolution.

• To see which of these items that have comments on them beyond Mjs comment (belwo) use this link

---

SCs currently marked as: Applies directly as written [MJ's INITIAL recommendation in square brackets] those marked [MJ:AAW] always ask if notes might be needed.

• 1.2.6 Sign Language (Prerecorded) (Level AAA)
  - [MJ:AAW - any notes needed?]
• 1.2.7 Extended Audio Description (Prerecorded) (Level AAA)
  - [MJ:AAW + 2 add two notes. Are these 2 notes above (taken from 1.2.3 Audio Description or Media Alternative) sufficient? Any other notes needed? ]
• 1.2.8 Media Alternative (Prerecorded) (Level AAA)
  - [MJ:AAW - any notes needed? Any notes needed for Closed functionality?
• 1.2.9 Audio-only (Live) (Level AAA)
  - [MJ:AAW - any notes needed? any considerations for closed functionality?
• DONE in PR Add 1.3.6 Identify Purpose (Level AAA) #817: 1.3.6 Identify Purpose (Level AAA)
  - [MJ:AAW but Possible notes needed because the concept of "regions" and having those be programmatically determinable may not be available for all non-web software and closed functionality (and maybe non-web document) technologies. Unsure if, across the board, programmatically determinable region attributes are available. ALSO For the definition of "region", would need to provide non-HTML examples of how one might designate a region, if it's possible.
• 1.4.6 Contrast (Enhanced) (Level AAA)
  - [MJ:AAW This doesn't seem to require additional notes. ]
• 1.4.7 Low or No Background Audio (Level AAA)
  - [MJ:AAW This doesn't seem to require additional notes.]
• 1.4.8 Visual Presentation (Level AAA)
  - [MJ: This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.8, replacing “browser or other user agent” with “@@ TBD replacement non-web language @@” in Note 1.
  - What would replacement language be for "browser or other user agent"?
  - Are there other notes needed for this SC?
  - Do you agree that no interpretation of the glossary terms is needed?
• 1.4.9 Images of Text (No Exception) (Level AAA)
  - [MJ:AAW This seems straightforward. Are any additional notes needed?]
• 2.1.3 Keyboard (No Exception) (Level AAA)
  • [MJ:AAW but NOTE 1: @@ TBD: Probably need to look at other keyboard SCs to see if any/all of those notes should apply to this SC.@@
• 2.2.3 No Timing (Level AAA)
  - [MJ:AAW - any notes needed?]
• 2.2.4 Interruptions (Level AAA)
  - [MJ:AAW - any notes needed?]
• 2.2.5 Re-authenticating (Level AAA)
  • [MJ:AAW -- but Does this need any notes? For example, are there technical limitations or regulatory requirements to not keep data so the when a user re-authenticates that would prevent data previously entered from still being available?
• 2.2.6 Timeouts (Level AAA)
  - [MJ:AAW - any notes needed? Any considerations closed functionality? Any word substitution or notes needed for the definition?
• 2.3.3 Animation from Interactions (Level AAA)
  - [MJ:AAW - Are there any notes needed or considerations for closed functionality? Is there any guidance or additional examples needed for the term 'motion animation'?
• 2.4.9 Link Purpose (Link Only) (Level AAA)
  - [MJ:AAW but Any notes needed for non-web context? Any considerations for closed functionality?
• 2.4.10 Section Headings (Level AAA)
  - [MJ:AAW] Are any notes needed non-web documents or software? Any considerations for closed functionality?
  - Seems that the glossary term could be added to the Glossary terms that apply to all technologies section. Agree?
• 2.4.12 Focus Not Obscured (Enhanced) (Level AAA)
  - [MJ:AAW but Any notes needed for non-web context? Any considerations for closed functionality?
• 3.1.3 Unusual Words (Level AAA)
  - [MJ:AAW but Might need notes on this, as I doubt there is a lot of existing support for this in non-web software. Not sure about support in non-web documents either.
  - Need to consider what notes might be appropriate for this SC, considering there may be a lack of platform support for this like there is in the Web. Same goes for closed functionality.
• 3.1.4 Abbreviations (Level AAA)
  - [MJ:AAW but Are notes needed for where platforms and/or non-web document formats do not support this?
  - What notes would be needed for non-web software, including platforms
  - What notes would be needed for non-web documents
  - Any considerations for closed functionality?
• 3.1.5 Reading Level (Level AAA)
  - [MJ:AAW Consider what notes might be needed for this SC. Currently WCAG has no exceptions built in.
  - Are notes needed for closed functionality?
  - Definition of supplemental content - should a similar example found in non-web contexts be exchanged for the first example?
• 3.1.6 Pronunciation (Level AAA)
  - [MJ:AAW but Not sure of support for this in a non-web environment, so notes may be necessary. Are additional notes needed for closed functionality?
• 3.2.5 Change on Request (Level AAA)
  - [MJ:AAW Consider what notes might be needed for non-web software and documents Are there considerations for closed functionality?
• 3.3.5 Help (Level AAA)
  - [MJ:AAW but May need notes.
  - Any notes needed for non-web software or documents?
  - Any additional considerations for closed functionality?
  - Do you agree that no interpretation is needed for the glossary term?
• 3.3.9 Accessible Authentication (Enhanced) (Level AAA)
  - [MJ:AAW Are notes needed for non-web software and documents? Are there considerations for closed functionality?

SCs currently marked as: Applies directly as written, changing "user agent" to "user agent or platform software"

• 2.4.13 Focus Appearance (Level AAA)
• 2.5.5 Target Size (Enhanced) (Level AAA)

SCs currently marked as: Applies directly as written, changing "web content" to "content"

• 2.5.6 Concurrent Input Mechanisms (Level AAA)
• 2.3.2 Three Flashes (Level AAA)

SCs currently marked as: Applies directly as written, changing "web pages that require" to "content that requires"

• 3.3.6 Error Prevention (All) (Level AAA)

SCs that have "set of web pages" in the SC language

• 2.4.8 Location (Level AAA)