- From: Bruce Bailey <Bailey@Access-Board.gov>
- Date: Fri, 15 Mar 2024 22:18:07 +0000
- To: WCAG 2.x issues list <public-wcag2-issues@w3.org>
- Message-ID: <MW5PR22MB35112AAD3983144637A03320E3282@MW5PR22MB3511.namprd22.prod.outlook.com>
We continued our discussions about SC 1.4.10 Reflow<https://www.w3.org/WAI/WCAG22/Understanding/reflow.html> and how the related Understanding documents can be improved. Attendance (10): Alastair Campbell, Bruce Bailey, David Cox, Francis Storr, Giacomo Petri, Gundula Niemann, Laura Oakly, Marco S. (my apologies), Patrick Lauke, Scott O’Hara. Regrets from Mike Gower and Duff Johnson. The group has consensus that a nuance approached should be used for evaluating as to what counts as a chuck of content for avoiding scrolling in two dimensions. One example is carousals. Typically, a carousal scrolls horizontally while the containing page scrolls vertically. This is not automatically a failure against the SC. The meaningful chunks of content within the carousal (i.e., the horizontal scrolling content) is what must not exceed a height equivalent of 256 CSS pixels. Obviously, it is a challenge is to write this out well enough in Understanding. The other major concern is what is fair to allow for the exception (other than the easy example of data tables). Scott volunteered to refine what he has started in the Reflow scratchpad<https://docs.google.com/document/d/1NhXS0Gfdsgl67pIhK0BYmayTq_v45CJMP0Ve36Uui3Q/edit#heading=h.ig5yieqnscye>. We need more examples. Thumbnails are okay, but code will be needed as well. We also looked at a few For Discussion items from the Board. * add lang attribute to document by fstrr · Pull Request #3740<https://github.com/w3c/wcag/pull/3740> merged as bug fix. * 1.4.1 Use of color: adding examples to understanding text by detlevhfischer · Pull Request #3717<https://github.com/w3c/wcag/pull/3717> back to In Progress * Remove "1280 pixels wide" test step from F94 by patrickhlauke · Pull Request #3739<https://github.com/w3c/wcag/pull/3739> back to In Progress Next week (March 22nd) we are back to our standing agenda<https://github.com/w3c/wcag/wiki/Meeting-minutes-index#standing-agenda>. 1. Review ‘For discussion’ items. 2. Review ‘Drafted’ items (30 min), either: * move back to In progress, with more work to do; * move to Ready for approval, if there is general agreement the issue is sufficiently resolved; or * leave in Drafted, if discussion was not concluded satisfactorily. 1. Review ‘To do’. 2. Time permitting, items of interest to participants, including open discussions.
Received on Friday, 15 March 2024 22:18:15 UTC