-
Notifications
You must be signed in to change notification settings - Fork 281
2025‐03‐07
Attendance (10): Mike Gower, Alastair Campbell, Gundula Niemann, Patrick Lauke, Giacomo Petri, Francis Storr, Bruce Bailey, Ken Franqueiro, Scott O'Hara, Lori Oakley
- Time change Sunday 9 March in U.S., W3C meetings (pinned to U.S. Eastern/Boston) may be at different times than usual for the next few weeks.
- CSUN is next week and most AG WG meetings are suspended, except for a marathon hybrid meeting Monday, March 10th.
- We will be having backlog call as per usual.
- Bruce regrets for 3/14 and 3/21.
- Per agenda email we are following our Standing Agenda.
- We need more candidates in drafted please.
No as much feedback (from AG) as we might like to Updated Understanding Reflow. This week Mike shared interesting example with a Japanese site, where vertical text scrolls vertically (only) but is hard to track text even without there being horizontal scroll bars. The controversial examples fall within the prescribed metrics. Ken pointed out that it is a no-win situation, so technically a pass with poor usability. Giacomo points out that we could not address the example without changing normative language. In thread, Mike has an analysis which Scott agrees with. Scott has gotten positive support off-line, and during the pinged a few folks for thumbs-up or approval reviews. From previous experience we are happy to have thumbs-up from outside the WG. Ken has Scott's blessing on his adder. Moved to Fully Reviewed. Huzzah!
Move H28 from sufficient to advisory in 3.1.4 Abbreviations SC #4195 has been discussed on on few recent calls. Giacomo has addressed all previous feedback. Advanced to Fully Reviewed.
Update index.html to correct alphabetical order #4256 split off from another normative correction to have the errata as atomic as possible. This change is switching the position of User Inactivity and User Interface to make them listed alphabetically. Moved to Ready for approval, but kept as draft as Mike wants to close out the combined PR first.
Update user-inactivity.html #4122 adds a css "note" class to the paragraph following the definition (as is the pattern for other glossary terms). Change was previously discussed and approved. Kept in Ready for approval.
Eight items queued up from previous weeks.
Issue Restore the need for accuracy/correctness to 3.3.2 Labels or Instructions #3984 was discussed previously and originally tagged as Response-Only. The question comes up periodically, and it is a fair point that Labels and Instructions need to be accurate to count as being provided under 3.3.2. Response-Only label removed.
3984 labels descriptions #4212 closely related to 3984 and led to some phrasing improvements for Understanding. Patrick had an edit to change a parenthetical to a sentence. Moved to Ready for approval.
Update Working Example ARIA24 #1016 morphed into a total rewrite rather than an update. Technique adds hidden text, and it is addressing more than original issue. It is using HTML plus CSS rather than ARIA. PR no longer closes #1007 and F87 is being revisited. Lori volunteered to review. Stays in Drafted.
1.4.2 Audio Control - Do two-way voice communications features and/or video conference features need to meet this req? #4230 revisited question from Glenda. We have talked about this one a couple times. In thread, Mike has proposed something which could be added to Understanding. Previously we had discussed that muting tabs, a common browser feature, is not sufficient for meeting the SC. Volume control for live audio is a good idea for WCAG3 and is a requirement of other ICT accessibility standards, but not part of SC 1.4.2. Mike volunteered to draft a PR. Removed Response-Only label but left in Drafted.
Replaces the previous name of the working group in Understanding #4257 aims to correct "WCAG Working Group" to "Accessibility Guidelines Working Group". Mike volunteered to reviewed, and shortly after the meeting found other instances which need correction. Remains in Drafted.
1.2.3 / 1.2.5 Audio description - right language required? #3873 asks about audio description not using the same human language as the rest of the web page. We have concurrence that would not meet the SC.
Alternatives match language #4262 by Mike aims to address the above issue by borrowing from Conforming Alternative Versions, other SC, and Understanding where “in the same human language” is explicitly part of the requirement. Mike had some concern that he may have inadvertently changed a glossary term (which would be normative) rather than Understanding and Techniques. Needs additional quality review. Left in Drafted.
Patrick reminded group that we have old issues ripe for resolution, How to add audio descriptions to videos? #1768. Question is similar in that it is also about Audio Description not being being of sufficient quality — due to lack of gaps in dialog.
Improve wording of first example for path-based gesture #4268 discussed briefly, left in drafted.
Please take a look at Revisit figcaption styles #4241 for improving presentation of figure captions on repo. Remains In Progress.