-
Notifications
You must be signed in to change notification settings - Fork 250
2024‐05‐03
Attending (9): Michael Gower, Alastair Campbell, Bruce Bailey, Patrick Lauke, Avon Kou, Francis Storr, Giacomo Petri, Lori Oakley, Scott O'Hara
We've resolved about 100 issues, but net count is about the same. Patrick made the good suggestion that we might what to shift to a PR focus. Focus on done versus what is left to do.
More comments in latest draft, no other discussion.
- Review ‘For discussion’ items
- Review ‘Drafted’ items (30 min), either:
- move back to In progress, with more work to do
- move to Ready for approval, if there is general agreement the issue is sufficiently resolved
- leave in Drafted, if discussion was not concluded satisfactorily
- Review issues closed and project items closed.
- Review ‘To do’.
- Time permitting, items of interest to participants, including open discussions.
Technique G183: expand example 2 to actually illustrate the technique's point #2244 3.3.1 it is a bit circular icons (e.g. caution sign) with alt count as "text". TF members, please take a look.
Update F73 to remove example 2 #3743 about using only hover-on-underline to indicate links. Mike reminded group that with 2.2, AG WG tried (and was not able) to specifying when underlining for links (e.g., in a menu) is sufficient (or not). Group decided to regain F73, based on Note 3 of Understanding Use of Color.
Tweak understanding for 1.2.3 and 1.2.5 #1790 Address a gap that current Understanding does include audio ducking, even though that is not uncommon. There is an accessibility gap when if narration is added only during pauses (in dialog) is not sufficient for the visual information being conveyed. TF consensus was for splitting into one or more additional techniques. (Extra one possibly for ducking dialog to defer to AD.) Need to check if issue is open on lack of gaps (in dialog) being a failure (or not).
Editorial update to target size (minimum) exceptions #3189 noting that this is (class 2) errata.
Remove F87 #2800 Scott pointed out use of deprecated CSS code. Also CSS ::before
and ::after
now is accessibility supported. No objections to removing technique, but there were errors when building. Patrick volunteered to debug that.
Rewrite for 3.3.1 Error Identification understanding document #1651 looks fine, but needs a review. Giacomo volunteered.
Technique G183: expand example 2 to actually illustrate the technique's point #2244
Review issues closed and project items closed.
Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on hover for links or controls where color alone is used to identify them (G183) procedure at bottom conflicts with other Understanding. Scott suggests that clarity could be smoothed over by harmonizing with advisory technique. Concurrence on the call is that the very beginning created a lot of confusion before Patrick added the NOTE in the understanding doc.
Alstair made a suggestion for 2244
- Old: We have a dozen items for approval by AG, due 4/29. Going forward, we may want to have fewer than that.
- Old: The project board, and our calls, are oriented to Pull Requests.
-
old Change markers: add visual style and remove unnecessary text semantics #1481 is just a change to style sheet, and will be bundled with other erratum. Moved to Ready for approval.
-
old Rewrite for 3.3.1 Error Identification understanding document #1651 has four thumbs up, but is long discussion thread. TF members are asked to take a look and thumbs up if you can in good conscience. Use of the word "must" might be problematic. Moved to Ready for approval with four thumbs up.
-
old Add sufficient technique for 2.4.7 using :focus-visible #3272 Alastair noted that, since it is new, we need to double check the numbering (used for the filename). At present, there are 43. See Listing of all CCS techniques and techniques/css file listing in the repo.
- old Expand 1.4.10 Reflow note about 200% and breakpoints, add matching note to 1.4.4 Resize Text #2630 discussed very briefly. TF members asked to take a look and thumbs up or comment.
-
old Update video-only 1.2.1 Understanding document #3802 looking for a volunteer. Looks like it could be straightforward.
-
old Focus not obscured (minimum) and scrolling content into view #3801 discussed. Scott is working on this one and looking for feedback from group. SC is dependent upon behavior of keyboard focus. Keyboard focus going behind pop-up can be reveled by scrolling, but that is what the SC is trying to address.
At end of call, there was some brainstorming between Alastair and Francis on how to test with local builds, deleting and replacing folders to unify files between 2.1 and 2.2, to clean up structure. With 2.0 may need manual mapping. Banner over old Understanding documents in TR space would be helpful. https://github.com/w3c/wcag/pull/3270/files