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

Revision to Understanding Reflow

From: Wayne Dick <wayneedick@gmail.com>
Date: Mon, 12 Mar 2018 13:06:24 -0700
Message-ID: <CAJeQ8SBha-oKCETskHGuwViDuMZO=+CsgE3OW0KMkVCpvph+nA@mail.gmail.com>
To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
​Note: New content is underlined. Perhaps we could discuss this at the LVTF

Data [del "complex"] tables have a two-dimensional relationship between the
heading *cells* and data cells. That *structural* relationship conveys the
meaning of table content.
​Thus, the reflow
 success criterion does not apply to
​the ​
*structure* of data tables.
*Rows and columns are not required to ​reflow to fit viewports*.

*A simple table cell is one that does not contain another table. The
content within a simple table cell does not have a two-dimensional semantic
relationship to protect. Thus, the exemption for data tables does not
extend to the content of simple data cells.*
Lastly, interfaces which provide toolbars to edit content need to show both
the content, and the toolbar in the viewport. Given enough buttons, that
toolbar may need to scroll in the direction of text (e.g. horizontally in a
vertically scrolling page).
*While toolbars may extend beyond​ ​viewport boundaries, ​the​text within
editing or reading areas must ​reflow. An editing / reading application
that does not ​reflow text for reading​ / editing is not functional*.
Received on Monday, 12 March 2018 20:07:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 12 March 2018 20:07:30 UTC