-
Notifications
You must be signed in to change notification settings - Fork 328
2025‐05‐23
Attendance (9): Alastair Campbell, Bruce Bailey, Dan Bjorge, Giacomo Petri, Gundala Numan, Ken Franqueiro, Mike Gower, Patrick Lauke, Scott O'Hara,
Regrets: Akash Shukla, Filippo Zorzi, Francis Storr, Lori Oakley, Steve Faulkner
- Reminder that we had items for REVIEW - WCAG 2 proposed changes (due by May 20).
- Refresh list REVIEW - WCAG 2 proposed changes (due by June 3)
- We are at top of hour for REVIEWS and AGENDA - AGWG Meeting May 27th 2025
- Items are listed below and available on the Project Board under column Sent for WG approval.
- Email Agenda, Following standing agenda, with obvious focus on any responses to date for Reflow
Updated Reflow understanding doc #4055 is merged and scheduled to publish and go live next Thursday (4/4). Meanwhile, Scott has also resolved a number of related issues and discussions. The use of Cloud Flare (mentioned above) is also incorporated with that publication. See Migrate Reflow videos out of repository #4308. The deploy preview is available.
Updates proposed and implemented by the WCAG 2 Task Force, providing a two-week window for Working Group members to review non-normative WCAG 2 updates, and consists of changes in several categories.
In addition to the non-normative changes in the sections below, the Task Force has identified a normative change for the Working Group. This is listed here to initiate a normative review process. It will be added to an upcoming call, and if the attending working group members are in general agreement, it will go through a CFC process.
Remove periods from end of definitions #4359
Changes that do not meaningfully alter informative language in a normative document.
Remove the confusing "not necessarily limited" part of the 1.3.4 Orientation note and expand #4349
Update understanding conformance and technique G73 to remove mention of longdesc #4365
Changes that meaningfully add or alter existing non-normative guidance.
Add link to NIST SP 800-63B 2nd public draft to 3.3.8 / 3.3.9 understanding #4351
Small improvements to language intended to clarify existing guidance.
Some editorial updates to Understanding SC 2.5.3 #4335
Responses to issues which we are not going to create a PR.
None this cycle.
Trivial editorial corrections such as typos and broken links)
Extra whitespace in 5.3.2 Optional Components of a Conformance Claim #4357
The following outlines the updates proposed and implemented by the WCAG 2 Task Force. It provides a two-week window for Working Group members to review non-normative WCAG 2 updates, and consists of changes in several categories.
Changes that do not meaningfully alter informative language in a normative document.
Changes that meaningfully add or alter existing non-normative guidance.
Meeting audio description through narration #4327
Small improvements to language intended to clarify existing guidance.
- Audio description Understanding covers "important" visual content #4324
- Update media-alternative-prerecorded.html #4326
- Time based media EO references #4339
- Update seizures-and-physical-reactions.html #4361
- Add note to 3.3.2 understanding to explain "require" in normative wording #4367
Items for which we are not going to create a PR.
None this cycle.
Trivial editorial corrections such as typos and broken links.
- Note #4166 and #4055 in Techniques change log #4391
- Replace incorrect/outdated statement about tech support in 3.3.1 understanding #4355
Audio description failure technique #4390 with preview for new F113 Failure of Success Criterion 1.2.5 due to not using available pauses in dialogue to provide audio descriptions of important visual content. Has not yet sent been for approval, but should be soon.
Tweak understanding for 1.2.3 and 1.2.5 #1790
4411 SCR 21 3652 3653 Pull request from when it was deleted 3652 could use comment. Deploy preview
Patrick walked group through Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding #4402. Additional prose and explanation regarding contrast essential exception for a logo. Would closes four (!) issues. There are situations where the author is obligated to do something even if logo remains unaltered.
Group has significant discussion around guidance is going too far and use of "should", which is historically problematic.. We had consensus on call for requirement for 3:1 somewhere, especially if logo used for UIC (e.g., a button). Can be especially sensitive when logo is a logotype (a.k.a., wordmark or lettermark). Unlike logomarks, which feature symbolic images, logotypes emphasize the brand's name itself and WCAG has higher expectation for images of text (as compared to images). We would not Understand to imply that the logo needs to be changed, but we do want to alert developers to issues. If the logo is only aspect which indicate a UIC, that has a 3:1 contrast requirement. Patrick will revisit. Keeping in For Discussion and group will revisit.
Update synchronized-media.html #4371 aims to clarify phrasing in note around synchronization as a generalized word versus the more specialized meaning used in WCAG. For example, aesthetic background music is "synchronized" but probably not to the extent required by Guideline 1.2 for Time Based Media.
The WCAG definition includes situations with time-based interactivity. An example is activating button when certain sound is played or images displayed. There is some concern that proposed edit obscures that use case.
Discussed Add note about transaction-amount to 1.3.5 understanding #4362 and the problem with transaction-about being autofilled inappropriately. Patrick added some clarification. Group had some concern that proposed PR was not quite finished. An option is to not provide this example, and leave the question unanswered. The note might be expanded to "The purpose of each input field collecting information about the user can be programmatically determined when:" ...and again it comes down to how can you argue an amount is about the user. Question raise, does that mean sites generally need a distinct name field across every single product page etc? That seems like a really easy thing to forget to do! Patrick offered to revisit.