-
Notifications
You must be signed in to change notification settings - Fork 328
2025‐04‐25
Attendance (10): Alastair Campbell, Bruce Bailey, Dan Bjorge, Giacomo Petri, Gundala Neuman, Ken Franqueiro, Mike Gower, Patrick Lauke, Scott O'Hara, Steve Faulkner
Regrets: Francis Storr, Duff Johnson, Lori Oakley
- Email sent to AG WCAG 2 proposed changes (review due by May 6) will be focusing for next week.
- FCPWD for Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile) expected to publish soon, since the CFC was weeks ago. Please consider planning to set aside time for your review. We don’t plan to provide feedback as a TF.
- Per email to list, standing agenda for today.
- One of the items under discussion is what to do with the ‘user inactivity’ PR.
- Please take a few moments before calls to see if you have any items in Drafts, so you are prepared to speak to them.
- Please be encouraged between calls to pick up To Do time and draft PRs or Issues.
- Friendly reminder that most docs in repo are HTML (not Markdown) and so paragraph
Pelements need to be entered (and closed) manually.
2.4.6-headings-and-labels-descriptive-icons #4147 few thumbs up and some discussion. Gundula has concern that ”common icon” are not universally understood. Patrick pointed but that we’re not requiring, at AA, that icons on their own can’t be used... Requiring retroactively that everything needs a visible text label would immediately make 80% of the internets fail and contrary to long-standing practices. Scott pointed out context matters so some ambiguity (e.g. hour glass might be ‘search’ or ‘more information’ or ‘zoom’. Many icons do not have tool-tips and tool-tips are not generally regarded as being universally available (but that can be okay).
GitHub used as an example of some icons being ambiguous to all users, and that is okay. It is an open question as to when an icon (only)is clear enough? In these cases it is fine, in others it is not. Always having plain text available would be a new requirement.
This is a quality issue for WCAG 3, and WCAG 3 may want to go further and require visible text labels. Another example is where placeholders icons disappear, and then there is a failure. Sufficiently of ALT is similar as an unresolved issue.
Flagged Update user-inactivity.html #4122 which proposes to add CSS note class to the paragraph following the definition. We have discussed on call a few times now. Left in For Discussion.
Flagged Update redundant-entry.html #4282 being developed. It proposes substituting “session” with something else. Please see the conversation thread for the reasoning. Left in For Discussion so we might get consensus, please thumbs up or comment during the week.
Briefly discussed Is it possible to turn on a platform's 'increase contrast' mode when testing WCAG SC 1.4.3 Contrast (Minimum)? #4290 which is Response Only and has recent conversation. We will see if OP is okay with drafted reply. Left in For Discussion.
Flagged Tweak understanding for 1.2.3 and 1.2.5 #1790 as being an active online discussion. This and related issues (and PRs) will stick around until other changes related to 1.2 are resolved. Mike anticipates removing this item from the project board, as while less controversial edits are merged.
Meeting audio description through existing narration #4327 reviewed and moved to Ready for Approval.
Time based media EO references #4339 reviewed and moved to Ready for Approval.
WCAG 2 Backlog TF review of Label in Name Algorithm #4312 discussed and closed as our TF needs to wait on ACT to resolve issues already raised in their PR. For example, DetLev spotted raised an issue and commented “Not sure how to include this in the algorithm though.” Issue closed since there is not anything more which we can do for now.
Discussed SC 1.4.3 - Contrast minimum - note on evaluation success criterion using px - misleading px value #4337. TF has full concurrence with keeping 18.5 for the reasons Mike outlined in conversation thread. No one on call had concerns with leaving alone. Sentiment is that our discussion time is disproportionate to the alleged problem, and that things would only be made worse by making a change. Additionally, if passing depends upon a 100th of pixel. Consensus on closing. Moved to Ready for Approval.
Briefly discussed Fix unclosed tags in understanding pages #4353 which is entirely an editorial correction. Moved to Ready for Approval.
Reviewed and discussed Remove the confusing "not necessarily limited" part of the 1.3.4 Orientation note and expand #4349. Change is significantly more than originally proposed, but is now clarifying rather than being ambiguous. Moved to Ready for Approval.