-
Notifications
You must be signed in to change notification settings - Fork 256
2024‐07‐12
Attendance (13): Alastair Campbell, Avon Kuo, Bruce Bailey, Dan Bjorge, Filippo Zorzi, Francis Storr, Ken Franqueiro, Gundula Neuman, Mike Gower, Lori Oakley, Patrick Lauke, Sage Keriazes, Scott O'Hara
Regrets: Giacomo Petri
We're at the start of a new 2-week review round for the WG. See REVIEW - WCAG 2 proposed changes (due by July 23) sent to AGWG. As AG participants, TF members are encouraged to Thumbs Up. Generally look for addition Thumbs Up or positive comments. For technical bugs, AG approvals tend to fewer.
Welcome to Sage (they/them), who has also joined the ACT Task Force.
Following our agenda, plan is to go through a few things in Discussion, but instead of looking at In Progress may, potentially (if anyone is prepped), spend some time talking about Reflow or another meaty topic.
Otherwise, working from the Project Board.
Remove leftover references to Flash techniques #3540 is a longish discussion thread and lead to further conversation at end of the call (see below). Otherwise, no concerns identified with PR. It may not be useful, but does no harm. There has not been an auto generated build in some time, but for this PR, that does not matter. It is an open action item to resolve JSON dependances.
Updating example in On Input Understanding within note #2984 flagged by Patrick, but we ran out of time to discuss.
Update H39.html #2137 for caption element on tables could use addition Thumbs Ups or comment please from TF members. Mike will revisit.
Harmonise wording for techniques checks/steps #3915 use of hash (pound sign) for numbering. Improving consistency since numbering is US centric. EO (Shawn) plans to add to style guide and to address consistently with new staff person who starts soon. Stays in ready for approval.
Remove parsing related techniques #3961 lead to question if PR also needs to remove the links to those techniques in the understanding documents. Left in Drafted for Ken to followup.
Fix typo #3938 on deck but did not get to.
Discussion about 3:1 contrast allowing for links using color. Also why underline or bold for links is of utility.
1.4.1 Use of color: adding examples to understanding text #3717 as compared to Changes to 1.4.1 Use of Color understanding #1788 was the subject of discussion.
Gundala raised issue with examples. While this is Understanding for 1.4.1, we would not want to have example that fails a different SC. We noted that example does not pass AA contrast requirement, fails focus-appearance because less than 3:1. Revision should note the example fails focus-appearance. Needs update for initial state. Example is okay, but needs clearer failure first. It would be useful to include the basic example for link text without a underline before this more niche case. Basic example is the common case, and skimming the document it wasn't as clear as this niche case. Potentially misleading as written. Add paragraph before initial paragraph under Focus.
Detlev asked to update. PR 3717 reverted to In Progress. Mike will revisit PR 1788.
We has a conversation regarding techniques for obsolete technologies (e.g., Flash, Silverlight). Ken continues to iterate on new technology stack (11ty) and preview builds (Netlify). There is a good deal of cruft from the now unused code base (e.g., XSLT). Most of the previous features have been replicated and integrated. Some of the legacy code provided by XSLT are still a work in progress, such as treatment of obsolete Techniques, are still a work in progress. There different expectations for some of the 2.0 and 2.1 materials. (For example, for 2.0, it may be desirable to retain legacy Flash and Silverlight techniques.)
For technical bug fixes, there is not an expectation that Ken needs to put issues or vet PRs through this TF (nor AG) for approval. editors.css reference but not up to date, so GitHub.io not rendering well.
Ken replacing previews and builds with Netlify. For an example, see: https://wcag2.netlify.app/techniques/
Reflow scratchpad updated during call. Scott has added, but not finished. Alastair had some questions for Scott on middle paragraphs. There are a couple examples without images, but Scott needs more feedback on prose, and if we have agreement, before creating illustrations. There is a balance between providing best practices without asserting more is requirement. Noted that examples are not about legacy hardware restriction, but provided as a convivence and feasibility.
Not too much was able to pulled from WCAG2ICT drafting.
Open question on if "pinch to zoom" bit can be updated. iOS and other support has improved in recent years.
Scott will review comments and feedback and continue drafting.
Clarification provided at end of call regarding TF Process and clarification of TF use of of Drafted status column and that For Discussion is used by facilitators and generally implies questions raised by AG WG. TF members please be encouraged to move items to top of Drafted column, as we generally work top-to-bottom on those.