Skip to content

2026–07–31

Kenneth G. Franqueiro edited this page Jul 31, 2026 · 1 revision

Minutes from meeting on July 31, 2026

Attendance (12): Patrick H. Lauke, Francis Storr, Gundula Niemann, Adam Page, Lori Oakley, Bruce Bailey, Giacomo Petri, Baldino Morelli, Ken Franqueiro, Filippo Zorzi, Steve Faulkner, Jonny James

Announcements

  • 4 items sent to AGWG this past Monday; 3 are response-only
  • TPAC sync between WCAG 2.x TF and ACT TF confirmed for Friday 9:45 AM

Drafted

  • #5236: Add extra (non-normative) note to the definition of "conforming alternate version"
    • Erratum, but non-normative
    • Relates to existing notes 4 and 7; this attempts to clarify and make explicit the requirement that a configurable version must satisfy all SC at the same time to qualify as a conforming alternate version
    • Lori: this glossary definition has a lot of notes already; would it make sense to collapse any of these into the actual definition (though that would be a normative change)?
      • Patrick: keep in mind that glossary definitions are intended to work when substituted in-line where the terms are used, and this one is already questionable in that sense given that the normative definition already includes a nested ordered list; adding another note seems the least likely to rock the boat
    • Bruce suggested avoiding "If the content" with an alternative suggestion using passive voice
      • Patrick opted for calling out "the content" specifically to leave no room for misinterpretation; this is referring to settings that the site (not the UA) is providing
      • Ultimately settled on current wording
    • Moved to Ready for approval
    • Separately, Patrick will have a look if we also want to mention anything along these lines in Understanding Conformance, e.g. under Techniques for Providing a Conforming Alternate Version
  • #5235: Change mention of "numbered item" to just "item" / "numbered technique" to just "technique"
    • Continuation of #5200
    • Ken: Checked with Kevin; we both suspect "numbered" was intended to refer to the numbers in the technique IDs; neither of us have any qualms with simplifying the wording. Furthermore, this PR converts one ordered list to unordered to avoid confusion between the list numbering and technique numbers
    • Moved to Ready for approval
  • #5241: Fix various grammatical errors
    • Supersedes two LLM-authored PRs by performing a more comprehensive 100%-human-conducted check which found additional similar instances
    • Will be merged as a bug fix and noted in email for next cycle
  • #4682: Updating language around full screen
    • Briefly glanced at whether this would be a quick review, but recalled this potentially opening a can of worms, as removing the "on a full-screen window" definition may lose information, but also the current definition is potentially problematic
    • Seems likely this really intended to mean "maximized", given it was written for 2.0, so some wording tweaks could be warranted either way (but those might put it in 2.3 territory)
    • Maybe mull this one over and come back to it next week
  • #5123: Fix 20 broken external links in WCAG 2.2 documentation (#4964)
    • Not a super-strenuous review on principle, but updates enough links that reviewing could take a while
    • Another good one to scan between now and next week

Discussions

  • Giacomo flagged F68 (and possibly others?)
    • We seem to be mimicking the computed name algorithm, but missing important bits, so it's only partial instructions
    • Do the failure techniques warrant a validation pass on procedures, and in cases where they reiterate an existing external process/specification, link to the external instead?
    • Adam: If we're already expecting testers to be savvy enough to do this level of code parsing, we could instruct testers to go look up the accessible name using browser accessibility dev tools

Clone this wiki locally