-
Notifications
You must be signed in to change notification settings - Fork 266
2024‐05‐10
Attending (8): Michael Gower, Bruce Bailey, Francis Storr, Giacomo Petri, Dan Bjorge, Scott O'Hara, Lori Oakley, Filippo Zorzi.
Regrets: Alastair Campbell, Patrick Lauke
TF Facilitators ask all active participants to self-assign To Do items from the Project Board and may assign one or two items between calls. Lori volunteered to work on a batch of files with broken links. Mike offered to send Lori a URL to help with filtering for those issues.
The By assignee tabular view has been tweaked to hide status:done so it is more streamlined.
Mike also highlighted how his practice is to remove Issues from the Project Board once there is a PR drafted or For discussion. TF members are encouraged to do that as well, since that reduces redundancy and the Board tracks PRs better than Issues. That said, please continue to have discussions in the Issue threads, and less discussion in the PR whenever practical to do so.
Mid way through the call there was some conversation about capitalization and web page versus webpage. The wiki style guide adds to (and links to) WAI and W3C style guides. It is work in progress, and not dogmatic.
Scott shared Update F91 to remove unrelated techniques #3821 moved to Ready for approval.
Francis shared Broken link fixes to 2.2 documents #3481 which took some effort to resolve merge conflicts, which can easily happen if the TF takes a long while to get to a PR. Moved to Ready for approval.
Francis shared make F73 less shouty to have F73 use fewer ALL CAPS. Moved to Ready for approval.
Expand video fix to #examples video #3794 moved to Ready for approval after checking that it was not already merged.
Update usability glossary deep link #3813 moved to Ready for approval.
We discussed 1.4.1 Use of color: adding examples to understanding text #3717 left in Drafted as it needs review. Lori volunteered to walk group through the PR next week.
We discussed Remove failure technique F87 #3818 since CSS support is better. Dan pointed out that browser support is still not fully integrated, but :before / :after are in accessibility tree and support by AT. Limitations (find, select) impart all users, and not just AT. There are useability issues, but consensus was that a Failure Technique is a high bar. It might also be possible to narrow the test procedure. Dan and Scott will follow up.
https://github.com/w3c/wcag/issues/3127 https://github.com/w3c/wcag/pull/3813
3776 https://github.com/w3c/wcag/pull/3776
Dan disagrees with change, as it makes less broad. Dan does not think it errata. Giacomo, why not TV. Scott O Harra reads like exhaustive list. Sott: it’d be way more behind a change like “…of web content regardless of what kind of device it’s being viewed on
Change to response
Please +1 or
https://github.com/w3c/wcag/issues/3750
https://github.com/w3c/wcag/pull/1790 SKIP
https://github.com/w3c/wcag/pull/3753 Ready for Approval
Giacommo brought up issue that ARIA is a translation issue.
Some conflict between ARIA and HTML with Accessilbe Name and explict and implict roles. Tables with captions is an example.
Which SC requires Tables to have Accessible Name? https://www.w3.org/TR/html-aria/ Conflict between ARIA rule 0 and author best practice to use explict rather than implicit.