Analysis of what to Incorporate WCAG 2.2 errata into WCAG2ICT

[maryjom]

This issue is to track analysis of what changes might need to be made to WCAG2ICT due to the WCAG 2.2 update. Issue #607 is for tracking implementation.

The following list of issues are causing changes in WCAG 2.2. Need to determine if there will be any content changes that would need to be incorporated into the existing text in WCAG2ICT:

• Check with @mbgower if this is the correct list of PRs that got incorporated into the republish of WCAG 2.2.

Results of conversation with Michael indicate that the easiest route to know the differences is to analyze a diff file between original WCAG 2.2 Recommendation and the December republish.

[pday1]

Mitch had a similar issue: 607

[maryjom]

@pday1 @ChrisLoiselle Mitch had a good idea that we do the analysis with this issue and the PR with changes on the other issue.

[maryjom]

@ChrisLoiselle @pday1 I asked Mike about the list of PRs incorporated into the latest WCAG, but I think it's harder to muddle through since PRs for Understanding docs and WCAG techniques are included in the list - they're all in the same repository. Therefore I've created a diff version between the earlier WCAG 2.2 and the newly published WCAG 2.2 that we can more easily work through.

• SC sections (first half)
• SC sections (second half)
• Definitions section

[mbgower]

Mary Jo, The below history of commits I sent you does not primarily show any understanding or technique updates. It seems to encompass changes to the spec only (with the exception of one or two merges that include both informative and normative, from when we were less disciplined). You’ll note the batch that got merged on Nov 19, after the CFC. I think that is the primary set you’re looking for, but this history also contains other changes which were not deemed necessary to go through the CFC process, since they are on non-normative parts of the spec, etc. https://github.com/w3c/wcag/commits/main/guidelines Perhaps I’m not understanding what you’re looking for? Mike From: Mary Jo Mueller ***@***.***> Date: Wednesday, January 22, 2025 at 11:51 AM To: w3c/wcag2ict ***@***.***> Cc: Michael Gower ***@***.***>, Mention ***@***.***> Subject: [EXTERNAL] Re: [w3c/wcag2ict] Analysis of what to Incorporate WCAG 2.2 errata into WCAG2ICT (Issue #580) @ ChrisLoiselle @pday1 I asked Mike about the list of PRs incorporated into the latest WCAG, but I think it's harder to muddle through since PRs for Understanding docs and WCAG techniques are included in the list - they're all in the same repository.  @ChrisLoiselle<https://github.com/ChrisLoiselle > @pday1<https://github.com/pday1 > I asked Mike about the list of PRs incorporated into the latest WCAG, but I think it's harder to muddle through since PRs for Understanding docs and WCAG techniques are included in the list - they're all in the same repository. Therefore I've created a diff version between the earlier WCAG 2.2 and the newly published WCAG 2.2 that we can more easily work through. We can divide the work by thirds: 1. Definitions section 2. SC section (first half) 3. SC sections (second half) — Reply to this email directly, view it on GitHub<#580 (comment) >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADNCZBJ3NL3EHVWU34YWWST2L7ZD5AVCNFSM6AAAAABQYFLG6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBYGEZTEOBVGU >. You are receiving this because you were mentioned.Message ID: ***@***.***>

[maryjom]

The diff file made this analysis easy, so I identified changes of note throughout in the list below. Now we simply have to determine if these things cause any changes within WCAG2ICT interpretation language. Daniel can handle the update of the directly quoted WCAG text.

• Everywhere in document "Web" changed to "web", "Website/Websites" to "website/websites", "web site/web sites" or "Web site/Web site" to "websites" or "website" (See PR 675)
• Everywhere in document "Success Criteria/Criterion" changed to "success criteria/criterion" previously accomplished - no changes needed.
• Anywhere "HTML" is used added markup to have the abbreviation expanded on hover to "HyperText Markup Language"
  <abbr title="HyperText Markup Language">HTML</abbr> is added via a post document build script - not in the source code. Will spawn off a separate issue for Daniel since this is done in scripting rather than directly in the markdown.
• SC 2.4.11 Focus Not Obscured (Minimum) Note 2 added "visually" to the text. NO action needed Applies as written, we don't include notes.
• 2.5.1 Pointer Gestures, 2.5.2 Pointer Cancellation, 2.5.7 Dragging Movements changed "i.e." to "i.e.," in the notes (also found in Comments on Conformance section) (See PR [Editorial] Incorporate Dec 2024 WCAG 2.2 editorial changes  #676)
• 2.5.8 Target Size (Minimum) changed "where:" to "when:", changed the definition list to remove ":" on each term, and changed "User agent control" to "User Agent Control" (also found that WCAG2ICT wasn't using definition list markup so fixed that at the same time) (See PR [Editorial] WCAG 2.2 editorial changes - update 2.5.8 "where" to "when" and make list a definition list #677)
• 3.1.2 Language of Parts changed "text." to be text." (See PR [Editorial] WCAG 2.2 editorial changes - add links to SC 3.1.2 for "text" and 4.1.2 for "states" #678)
• SC 3.3.8 Accessible Authentication (Minimum) changed "Web site." to "website." (See PR#675)
• 4.1.2 Name, Role, Value changed "states," to "states," (See PR [Editorial] WCAG 2.2 editorial changes - add links to SC 3.1.2 for "text" and 4.1.2 for "states" #678)
• accessibility supported glossary term - changed "Web Technology" to "web technology" (See PR [Editorial] Change "Web" to "web" #675)
• "Cognitive function test" glossary term made "cognitive" lowercase, changed "Web sites" to "websites" (See PR [Editorial] Change "Web" to "web" #675)
• "Content (Web content) glossary term, lowercased "web" (See PR [Editorial] Change "Web" to "web" #675)
• Removed unused, unreferenced glossary term "encloses" (See PR [Editorial] WCAG 2.2 editorial changes - update Comparison with the 2013 Note to remove "encloses" #679)
• Glossary term "non-text content" changed "ASCII Art" to "ASCII art" No change needed since WCAG2ICT already lowercased "art"
• Glossary term "programmatically determined link content" changed "paragraph, list" to "paragraph, list item" No change needed since we have no guidance
• Glossary term "programmatically set" not sure but seems to have some change to "user agents" No change needed since we replaced "user agents" in the definition.
• Glossary term "single pointer" underwent pretty extensive changes. Will need to check if we need to do an interpretation. No change needed since we have no additional guidance for this term

18. Glossary term "status message" added a link to "process" No change needed since we have no additional guidance for this term
19. Glossary term "technology (Web content)" changed to "technology (web content), "Web Technology" to "web technology" and "Web Content Technologies" to web content technologies" changes done with PR about capitalization.
20. Glossary term "used in an unusual or restricted way" changed "WCAG 2.1" to "WCAG 2" No changes needed since WCAG2ICT has no additional guidance for this term.
21. Glossary term "encloses" was removed, so remove from WCAG2ICT terms that apply to all technologies section.