-
Notifications
You must be signed in to change notification settings - Fork 332
2025–11–21
Attendance (13): Bruce Bailey, Dan Bjorge, Alastair Campbell, Ken Franqueiro, Mike Gower, Patrick Lauke, Scott O'Hara, Lori Oakley, Giacomo Petri, Francis Storr, Duff Johnson, Baldion MOrelli, Roland Buss
Regrets: Gundula Niemann, Patrick Lauke
- WCAG 2 proposed changes (review by Dec 1) items sent to AG.
- AG members asked to Please review by 2 December Current editor’s draft of WCAG2ICT Group Note. This is not something we will do as a TF.
- Per agenda email touch on:
- TPAC
- WCAG 2.next
- Then standing agenda.
From TPAC 2025 slide recap
- WCAG 2.? Recommendation with normative updates, no additional requirements
- The WCAG 2 backlog task force continues to lead the WCAG 2 cleanup effort
- including addressing the internationalization needs
- WCAG 2.?
- Out for public comment Q3 2026
- Publish Q3-Q4 2027
- Among others, see minutes from TPAC on WCAG 2.2 and non-Latin languages.
The possibility of another iteration of WCAG 2.x raised as possibility at Tuesday AG call. See minutes and slide:
- What are our goals for WCAG 2?
- Address internationalization needs to better support adoption
- Settle interpretations of current language to reduce debate for developers and testers
- What are the options?
- Add clarifications to understanding/technique documents
- Add forward looking editor notes only as a “WCAG 2.2.1” (name to be decided)
- Publish a new version
- Key factors:
- Time boxed
- Things which support WCAG 3
- Proposed scope of changes
- Backwards compatibility
- Examples of updates
Backlog TF asked to “make a list”. TF facilitators have not discussed, and don't want to spend much time on the issue today. Not making any decisions on this call. Prioritization on SC which people are interpreting differently (e.g., 1.2.5).
There are uncontroversial draft responses which we can treat as we do bugs. This would cut down WG churn.
Focussing today on some response only items.
Concern that PDF techniques page not accessible #1090. Issue raised doesn’t fail a particular SC. No substantive updates from TR space to WAI version. Left in drafted.
G82 Technique title (SC 1.1.1) #2118 discussed Draft Response as G82 has been updated. Left in drafted.
Applicability of map markings to SC 1.4.11 #2025 raises issue that complex map will be impossible to make all elements have contrast with each other. Bruce volunteer to review.
Technique using progressbar role #4686 discussed, including preview and working example. There are some caveats, which are described. Francis may need to check number of technique. Moved to Ready for approval.
Discussed Dan's adder to Minimum bounding box and line wrapping - unclear definition #3376 which is similar to ToC question. The answer remains that there needs to be 24 ccs px spacing between hypertext. Group has consensus that example of words used for navigation are not a "block of text" and so the inline exception is not applicable. Example shown would also have similar challenge as with breadcrumbs. Mike agreed to take a closer look. Left in Drafted.
SC-1.3.1 - paragraphs not semantically coded #4759 discussed as it seems like the same issue with paragraph definition per HTML specification. See definition for paragraph in wcag and html definition for paragraph. We want authors to use correction semantic element, but essentially everything is a paragraph.