-
Notifications
You must be signed in to change notification settings - Fork 339
2025–10–24
Attendance (15): Francis Storr, Bruce Bailey, Lori Oakley, Mike Gower, Filippo Zorzi, Scott O'Hara, Giacomo Petri, Dan Bjorge, Adam Page, Baldino Morelli, Patrick Lauke, Ken Franqueiro, Roland Buss, Alastair Campbell, Gundula Niemann
- Daylight savings time goes into effect differently in the next few weeks. This meeting uses 11:00 Easter (Boston) which shifts Week of 2 November.
- WCAG2-Issues, and Audio Description, discussed at the top of the Tuesday AGWG meeting. WCAG 2 proposed changes (feedback requested by 30 October) is also on the AG agenda for 10/28.
- CFC on Quarterly WCAG 2 Errata ends Monday, 10/27. Probably can be published to TR space in November.
- W3C Web Content Accessibility Guidelines 2.2 approved as ISO/IEC international standard on 21 October. Incorporation of errata since December 2024 publication is a work in progress.
- Per agenda email and paraphrase, our standing agenda.
-
Add section on native browser form validation to 3.3.1 understanding #4431 Discussed on call and concurrence that in actual practice, this is a FireFox bug. Moved to Ready for Review.
-
Clarification: Is a + / – button a sufficient accessible alternative for pinch zoom if users can't control the zoom focus area? (WCAG 2.5.1) #4692 discussed and reviewed WG comments, including mention of need keyboard method (which is bit tangential to the Issue raised. This is a Response Only item, and we made no changes made proposed response. Kept in Sent for WG review.
-
Add notes to 2.4.3 understanding to try and address static content receiving focus and what does/doesn't constitute a focus order failure #1643, we started to iterated on compelling feedback from Mitch Evan (of the WG). We like the clarification, but not sure if this Understanding doc is the best place for this detail. Mike will opened a new Issue but this PR kept in Sent to WG.
-
Add change log notes for removal of 4.1.1 #4668 flagged as having been discussed previously. Ultimately, just a one-line edit. Stays in Ready for approval.
3.3.2 - Form control labels using non-text content #4626 discussed previously and at length today. Patrick provided suggestion and the are since incorporated. Giacomo addressed phrasing on another recent PR. There is some concern for “usually” and “most” and “widely understood”. Also discussion around icons and common graphical labels (e.g., magnifying glass). Section is about form controls, so we might leverage that context. For iconography to be widely understood is very context specific; one example is flags for a language toggle. In original issue 3808 there is null alt for a flag graphic indicating country code. There can be difference between label for graphic and label for the drop down. With this example, many people would not be familiar country code or seeing this use for the first time. “Country code” is the label for the drop down and “+1” is the value. The Canada Flag icon is conveying meaning, but it‘s not a great label for label. There are multiple segments to a phone number, so multiple inputs and multiple labels. In some contexts, for example a multinational organizations intranet site, users could be expected to be familiar with country codes and flag icons used to make that selection. Other contexts, a country specific site for older people. Kept in Drafted.
Request for clarification: does Name, Role, Value include static states like "required"? #3523 flagged as needing resolution. Concurrence with closing and that original question raised has since been addressed. Bruce volunteered to address and then close.
Per email to list October 17th, review requested by Oct 30.
Changes that do not meaningfully alter informative language in a normative document.
None this cycle.
Changes that meaningfully add or alter existing non-normative guidance.
- Add notes to 2.4.3 understanding to try and address static content receiving focus and what does/doesn't constitute a focus order failure #1643
Small improvements to language intended to clarify existing guidance.
- Visual presentation: Improve wording of techniques instructions #4681
- Tweak inline code and preformatted blocks #4683
- Incorporate suggestions from restoration of Target Size (Enhanced) Understanding #4589
- Deduplicate entries under "This technique relates to" #4644
- Rephrase inline code elements #4623
- Replace raster images with SVG in Understanding SC 1.4.11: Non-Text Contrast #4573
For which we are not going to create a PR.
- Clarification: Is a + / – button a sufficient accessible alternative for pinch zoom if users can't control the zoom focus area? (WCAG 2.5.1) #4692
- Update F3 #1035
Already incorporated trivial editorial and technical corrections such as typos and broken links.