-
Notifications
You must be signed in to change notification settings - Fork 266
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. Understanding 3.3.1 is a bit circular with regard to icons (e.g., caution sign), since alt counts 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.
None.
Editorial update to target size (minimum) exceptions #3189 has consensus from TF and Ready for Approval. We noted that this is a (class 2) errata, but can be put into the batch with other errata already approved by WG.
Remove F87 #2800 is not controversial. On the call, 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. PR is otherwise ready for approval.
Technique G183: expand example 2 to actually illustrate the technique's point #2244 is Ready for Approval after some feedback on the call.
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) test 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. Alastair made a suggestion for 2244 which Patrick agreed with.
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).
Rewrite for 3.3.1 Error Identification understanding document #1651 looks fine, but needs a review. Giacomo volunteered. Status remains as Drafted.
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, there might be a need manual mapping. Alastair surfaced Update the 2.1 branch #3270 which shows some of the code needed.
We also discussed that adding a banner over old Understanding documents (in TR space) would be if utility.