-
Notifications
You must be signed in to change notification settings - Fork 256
2024‐10‐25
Attendance (11): Patrick Lauke, Giacomo Petri, Bruce Bailey, Francis Storr, Ken Franqueiro, Scott O'Hara, Lori Oakley, Gundula Nieumann, Fillipo Zorzi, Steve Faulkner, Dan Bjorge
Regrets: Alastair, Mike
- Backlog was an item on AG WG agenda call Tuesday, 10/22. Alastair highlighted the changes that will be added to the WCAG 2.2/2.1 updates for CFC.
- All recent Sent to WG have 5+ thumbs up, no thumbs down.
- Time shifts for daylight savings few weeks. AG times based on Boston, USA. (11/3 is change this year for Boston.)
Following our standing agenda, working from the Project Board.
Add explanation of what "automatic" means in 2.2.2 and 1.4.2, cross-reference #4012 straightforward edit, but long conversation thread which would benefit from one more review, and there is a merge conflict. Patrick offered to take a look.
For this call we focused on several older PRs which were causing merge issues. Merge issues are to be expected with the rebasing the Repo. The group provided feedback to Ken if the issues and PRs were relevant, or if some were clearly obsolete. Resolving the merge requests can be time consuming, so not a good use of time for PRs which might simply be closed.
Update F103 #1021 fixes Why is progressbar mentioned in F103? #892 discussed and deemed worth keeping. Left in Drafted.
link directly to new supplemental guidance #2296 is editorial and should be part of CFC for republishing of 2.2 to incorporated errata. Question if link should be to ...supplemental/about or just ...supplemental/ and if an anchor with doc should be a separate link. Left in Drafted.
update terminology per .../WAI/EO/wiki/Style#colorblind #2143 is uncontroversial and had consensus on call to incorporate. Left in Drafted.
Expand explanation of "repair techniques" #2566 worth retaining because 4.1.1 Parsing relevant to some people, but not something which will see new Understand since it is obsolete and 2.1 and 2.2. Patrick offered to resolve merge conflict. Left in Drafted.
Clarify title of Failure F108 #1211 briefly discussed and consensus on keeping. Ken explained behavior of title versus h1 in repo. Left in Drafted.
Update H95.html #2150 briefly discussed and had consensus on keeping. Steve Faulkner volunteered to doublecheck terminology and links. Left in Drafted.
Update G219.html #2500 Adding note to swipe gesture alternative to clarify that swiping alone would not suffice as alternative. Consensus on keeping, but needs checking for alignment 2.2 SC. Put to In progress.
Feedback to updated Reflow Understanding Doc being incorporated as it comes it. Preview link is available from top of PR. Looking really good, appreciation all around. Main bottleneck is illustrations and we are still waiting on directions as to where/how to upload animations.
Conversation thread worth reading as well. Among other details, Wayne Dick agrees that indented lists can be example horizontal scrolling cannot be avoided. Scott has gotten feedback and examples from colleagues inside and of Microsoft. Dan raised issue with recognizable branding (NPR), but had previous example using BBC. Patrick offered to help with illustrations. Some other related examples raised.
Giacomo shared reflow edge case where a single paragraph in isolation arguably avoids scrolling in two dimensions. Concurrence on call is that both examples fail. The directionally of language, reading order, is a factor when evaluating SC. Someone reading (left-to-right, presumably with magnification) reads across a line then has to relocate/reorient to far left of container. It is a barrier in actual practice and a scenario the SC was written to address.
Dan asked if we are intending to talk about a hypothetical version of this example where the 2nd panel isn’t scrollable? This can be scrolled both by a mouse gesture and with a keyboard in some ATs, so I think these examples are equivalent and both fail.