W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > November 2016

Re: Latest Reflow

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 1 Nov 2016 10:08:54 +0000
To: Wayne Dick <wayneedick@gmail.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-ID: <0E3AC7C2-574D-424C-967E-7384F4E79D2F@nomensa.com>
Wayne wrote:
> These are important changes in CSS that will make conformance difficult.  There may be new methods for declaring reading order that are programmatic.  So this requires watching. Maybe a Note.

I think it is worth noting the problems you get when trying to reflow a page. The significant ones I’ve run into are:
- Not over-riding “display: none” and similar things, you don’t want hidden pop-overs to appear all over the place.
- Needing to trigger the smallest media queries first. If you linearise a desktop size page, the order can be different to when you have zoomed or small-window view. This is most easily achieved by having a small window or zooming in first.
- Maintaining flexbox/grid ordering. The first thing you think when linearising a page is to wipe out float/positioning/flexbox/grid, but then the ordering not as the author has specified. Instead I’ve found it better to removing the widths and wrap them, rather than removing them.

I have in mind to do a blog post about this asking for other feedback, especially from devs. Is that an ok thing to do?

> SC (Reflow to Single Column) Content can be arranged programmatically …

Is it worth saying “content” instead of “text”? The order of images and other non-text content can be important.
Can we use some of the concepts from the ‘size all content’ SC? E.g:

Content can be arranged programmatically into a single column with all content in a correct reading sequence. Lines of text should not be truncated by the viewport unless the spatial layout of that content is essential to its use.

Also, I might guess that Andrew would say “the first sentence is essentially re-stating 1.3.2, in which case it could start “When content is arranged programmatically into a single column lines of text should not…”

Oh, and I updated the “sizing all content” SC to take account of your two-dimensional scrolling comment (replacing bi-directional).



Received on Tuesday, 1 November 2016 10:09:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:23:23 UTC