-
Notifications
You must be signed in to change notification settings - Fork 232
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.
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. Will close G63: broken link to usability glossary #3127
WCAG 2.2: Understanding 2.4.12 Focus Not Obscured (Enhanced) - Wrong reference to Focus Appearance #3753 entirely editorial and moved to Ready for approval. Closes Focus not-obscured understanding document #3722.
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.
Change "mobile devices" to "smartphones" #3776 discussed but TF did not get to consensus on phrasing. Dan disagrees with the change as it makes the example less broad, and that (as errata) it would be too much work. Giacomo suggested list should be modernized, for example to include Smart TVs. Scott pointed out that the phrasing gives the impression that it is an exhaustive list (which of course, it is not), and if we are making a change, broader phrasing like "...of web content regardless of what kind of device it’s being viewed on" would be a better. Bruce suggested adding "including but not limited to" to clarify that list are examples. PR meant to close issue WCAG Abstract section makes distinction between "tablets" and "mobile devices" #3750.
Tweak understanding for 1.2.3 and 1.2.5 #1790 looked at very briefly, and expected to be discussed on next call.
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.
At the end of the call, Giacomo raised a concern that ARIA is often a i13n translation issue (with the roles being English words).
Giacomo also noted that there can be conflict between ARIA and HTML, between Accessible Name and explicit and implicit roles. There is not clarity which as which SC are failed, and which elements impacted. Tables with captions is an example. Are tables required to have explicit Accessible Name? There is tension between ARIA rule zero (to use native HTML elements semantically), avoiding redundancy (i.e., having the same information in an ARIA role and from HTML attribute), and developer best practices to use explicit Accessible Name rather than implicit (for reliable output from screen reading software).