-
Notifications
You must be signed in to change notification settings - Fork 328
2024‐06‐14
Attendance (11): Mike Gower, Bruce Bailey, Alastair Campbell, Francis Storr, Filippo Zorzi, Scott O'Hara, Giacomo Petri, Dan Bjorge, Patrick Lauke, Gundula Neuman, Lori Oakley
Per agenda email, we are postponing an email to AG Working Group by a week. This is because we only have a couple items and because there was conflation between two pairs of PRs (two for 1.4.1, two for F94).
We worked from project board with the usual goal of quua few items to Ready for AG Approval.
Mike noted we have nine items in Errata for CFC column, so that is already enough to warrant publishing (and changing cover page date for TR track. Alastair prefers to collect a few more before sending for CFC, plus republishing 2.2 should wait on WCAG2ICT update to be finalized.
Remove "1280 pixels wide" test step from F94 #3739 since this is resize text and not Reflow, can be simplified. This PR combined with another PR already Ready for Approval.
Tweak understanding for 1.2.3 and 1.2.5 #1790 clarifies that if no gaps in dialog, AD will be weak (and so alternative should be provided) and lack of gaps in dialogue not sufficient at AAA. We may want to add new technique for ducking non-speech audio. Reply needed to Issue thread. Closes How to add audio descriptions to videos? #1768 which is very long discussion thread.
Added "Duplicated text" as guidance to fulfil the 1.4.5 Images of Text success criterion in the Understanding Document #3773 updated from recent feedback and on call. Patrick recommends borrowing more literally from the SC phrasing for the scenarios described. Mike askes to have guidance to have less overlap with from 1.1.1. Patrick noted that "technologies" is not specific vague and could understood to apply to, for example, limitations of the CMS (and not CSS/HTML specs). Giacomo is trying provide guidance so that authors who fail 1.4.5 (on its face), but have the information in text (and maybe CAV is applicable), do not have an incentive to skip providing machine-readable text. alternative text 1.1.1 to avoid failing both SC. Folks on call all agree that ALT value is not a way to meet 1.1.1. Folks on call also agree that with actual text nearby, so the text is on the same page (and per page-oriented conformance model), text is available and visible on the page and should not fail 1.4.5. Moved to ready Ready for Approval
Mike referenced 2.0 Understanding, notes that conflation with Guideline 1.3 is a long standing issue. Mike will rework with a new PR, try and keep clean. S
Mike argued (separately, on email) that shades of gray are not use of color as they have no color. On call, no one endorsed that perspective.
Patrick offers on CodePen Use of Color and State to help facilitate the discussion.
Changes to 1.4.1 Use of Color understanding #1788 and overlap with 1.4.1 Use of color: adding examples to understanding text #3717.
?? Added "Duplicated text" as a sufficient technique to fulfill the 1.4.5 Images of Text success criterion in the Understanding Document #3773 discussion deferred, as will not be quick. PR status remains as drafted.
?? Remove irrelevant preamble and first step from F94, future-proof expected results #3876 overlaps with Remove "1280 pixels wide" test step from F94 #3739 which is in already in Sent to WG queue. Keeping this PR in drafted, and Patrick will follow-up as needed.
?? how to ref techniques? is it more than <a href="../aria/ARIA24">ARIA24</a> ?
That discussion did not leave time on coordination call for time to reviewing Francis' Chore: delete stale branches #3878.