-
Notifications
You must be signed in to change notification settings - Fork 266
2024‐05‐17
Attendance (12): Alastair Campbell, Mike Gower, Bruce Bailey, Francis Storr, Patrick Lauke, Giacomo Petri, Dan Bjorge, Scott O'Hara, Filippo Zorzi, Gundala Neuman, Mike Gifford, Steve Faulkner.
Other AG WG activities competing for TF member bandwidth for the next few weeks:
- For Review: WCAG 3 Working Draft Outcomes
- WCAG2ICT on scheduled, and AG WG review anticipated soon
Happy Global Accessibility Awareness Day, yesterday. TF did a quick round-robin of activities and sharing.
- Mike shared highlights from internal IBM event.
- Bruce attend FCC DAC.
- Patrick reminded us that every day is Accessibility Day
- Alastair was part of 3-day event, Virtua11y web accessibility and digital inclusion conference. Presentations 2023](https://www.youtube.com/playlist?list=PLuo3RMjuSfpLWOExG7K3TzHH71vVVYoMU). Look for talks to get posted the next few week on Nomensa YouTube channel
- Scott shared local woes with UK vs US spelling of ARIA
- Francis had opportunity to do some evangelism
- Dan shared seeing a provocative demo by Cypress with its "test record" feature.
- Steve Faulkner joined our call to celebrate GAAD.
- Mike Gifford chaired an interesting panel.
- Giacomo gave a couple internal presentations on accessibility as mindset and announces setting priories for testing
On Tuesday, ten items sent to AG WG for REVIEW - WCAG 2 proposed changes (due by May 28)
None so far.
These will be queued up for an approval review by AG WG in a couple of weeks.
-
Remove "1280 pixels wide" test step from F94 #3739 Implication is there is base default size. Change removes starting setting.
-
Expand 1.4.10 Reflow note about 200% and breakpoints, add matching note to 1.4.4 Resize Text #2630 Edits are straightforward improvements to what is currently in Understanding. Illustrations would be welcomed, but those can be added as a subsequent Issue/PR. Some additions and clarifications were discussed. Please add questions or edits as you deem appropriate. Promoting to Ready for approval, but any TF should ask to move back to drafted if substantial edits are needed.
-
3818 Moved to Ready for approval.
-
3776 Smaller edit so this can be closed. Moved to Ready for approval. Dan agrees is closer to intent, but is normative (editorial) errata. Dan thinks it could be argued that example is expanding scope. Abstracts are informative.
-
3817 Syntax fix, move to Ready for approval.
-
1788 Giacomo has reviewed. Moved to Ready for approval
-
3765 Straightforward edit by Avon. Moved to Ready for approval.
2863
3854 Small edit updating link. M
[https://github.com/w3c/wcag/pull/3717](1.4.1 Use of color: adding examples to understanding text #3717) Patrick and Francis volunteered to review and provide editorial. Focus Visible seems to have a low threshold for "visible" (or not). Much discussion, left in drafted. Particked noted we closed 2.4.7 Focus Visible - what counts as "visible"? #302 is closed.
1790 Patrick will continue to work.
2906 closes 3863 PR needs more review as definition of "automatic" is vague. TF
When animation starts automatically with a change of focus, it's considered automatic. However, animation starting from pointer hover, scrolling, or changing a UI component is not automatic.
"Pause, Stop, Hide" applies to animations initiated by the web page. For animations triggered by user interactions, refer to 2.3.3 Animation from Interactions.
Things that start on page load vs on-focus vs on-hover. Discussion if new SC animation from interaction 2.3.3 overlaps. Steve asked to propose threshold.3773 Question if means text present at all time. Asking developers to replace images of text is something that improves accessibility. Duplicative text can be annoying.
Time permitting, items of interest to participants, including open discussions
Patrick: Understanding needs to bring in the idea of user intent. The wording Giacomo used does not imply it needs to be always visible, so a disclosure etc would be ok too.
Dan thinks that needs to be an erratum on the SC and not just a technique; I agree that it would be a reasonable exception to the SC, but I don’t think it is an exception and I don’t think a technique should invent exceptions
For new techniques, do not add numbers