-
Notifications
You must be signed in to change notification settings - Fork 232
2024‐06‐28
Attendance (14): Alastair Campbell, Bruce Bailey, Dan Bjorge, Filippo Zorzi, Francis Storr, Ken Franqueiro, Giacomo Petri, Gundula Neuman, Mike Gifford, Mike Gower, Lori Oakley, Patrick Lauke, Scott O'Hara, Steve Faulkner
Regrets: n/a
Following our standard agenda and working from the Project Board as per our usual routine.
We are meeting next week, notwithstanding the U.S. Holiday the day before.
Ten items sent to AG for review by July 8th. Please be encouraged to add your own thumbs up if you have not done so already.
There is a CFC for publication of WCAG2ICT Draft Note ending July 1st. This is consistent with the timeline for publishing WCAG2ICT draft for wide review. There has been a lot of constructive dialog between that work and members of this task force.
We will return to our discussion regarding Understanding Reflow in the near future, probably July 12th. In the interim, please review, comment, and contribute to the external reflow draft Google Doc.
Reserved for end of the call to talk about Understanding 1.4.1 Use of Color and 1.4.11 Non-text Contrast
Simplify/correct use of definition links #3930 We discussed syntax for linking to WCAG definitions last week. Ken affirmed he is doing QA on this build feature, resolving legacy respec issue. Ken noted that Conformance Challenges update should be it's own PR, since the review and build processes are different from Understanding et al. Patrick will split those off this PR. Kept in Drafted for now.
Added "Duplicated text" as guidance to fulfil the 1.4.5 Images of Text success criterion in the Understanding Document #3773 includes two new examples. Advanced to Ready for Review because it is unambiguously an improvement. Discussed during the call is that it's a bit confusing because the additional examples do not actually pass the criterion, but the page is passing by an alternative.
- Giacomo asked to open new issue for improving grouping of the examples, making it clearer if they are satisfying or failing the SC.
- Incidentally, it was noted that list presentation is different between 2.2 (DL) and 2.1 (UL). Ken affirmed that the code is different because the build processes is still being iterated upon.
Fix broken description paragraph for SM6 #3932 strictly a syntax correction and advanced to Ready for Approval.
Update broken link, remove double link in F47 #3701 editorial removing blink reference. Moved to Ready for approval.
Harmonize wording for techniques checks/steps #3915 split out from one particular PR to address globally (55 files) discussed. Alastair noted that aligning with the earlier examples is probably best (and the least amount of files changed), which is what Patrick has done. Francis will replace image to make failure more obvious. Lori agreed to add her review. Stays in Drafted for now.
Updates test steps in F94 #3739 Patrick corrected typo noted by Detlev. PR is already Sent for WG approval.
Update ARIA6 to close issue 317 #2358 by Francis and minor change made on call. Moved to Ready for approval.
Remove broken link in G56 #3702 dead link changed to Archive.org until such time that someone finds something better. Syntax error corrected on call and Moved to Ready for approval.
Add link underline color to 1.4.11 #3913 adds illustrations, fig caption, and other improvements to Understand doc. Moved to Ready for Approval.
Francis asked about fix broken link to on-focus document #3073 since he was having a build error, but discussion not quickly resolved. Left In Process.
Ken and Alastair noted many synchronization issues between 2.2 and 2.1 versions of documents. Plan is not too spend much time on 2.1 editions until build process is stable for 2.2. Then 2.2 informative material content can replace 2.1 all at once. Differences are too numerous address one file at a time. Goal is that it won't matter which path/link someone uses to get to the Understanding and related guidance.
Conversation regarding ambiguity around contrast for mouse-over effect. Hover effect on pointer is tricky to illustrate on static document. Francis has some concern with the prose. Checkbox is has contrast (against gray) but gray against white background does not have 3:1 background. See recent long discussion threads in 1.4.1 Use of color: adding examples to understanding text #3717 and Changes to 1.4.1 Use of Color understanding #1788.
Gundala pointed out pointer changing shape can be relied upon for visual indication with links. Giacomo disagrees that gray hover effect does not require minimum contrast against white.
We can keep moving current issues forward. Francis will create a new issue for adding or separating examples.
Mike clarified that Advancing from Drafted column to Ready for [AG] Review column should not be done by TF members. TF members should be comfortable moving items up (or down) within the Drafted column on the project board, so more easier/faster items are reviewed (and advanced) at start of meeting. TF members should advance issues/PRs from To Do to In Process, and from In Process to Drafted as appropriate.
The question Reminder that there is a style guide on the wiki for questions such as use of case, but plan is that a some point soon we will have large PR to conform many files at one go.