Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial draft update to reflow #3695

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Initial draft update to reflow #3695

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc94254
Initial draft update to reflow
alastc Feb 16, 2024
54e7780
Typo
alastc Feb 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion understanding/21/reflow.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ <h2>In brief</h2>
</section>
<section id="intent">
<h2>Intent of this Success Criterion</h2>
<p>The intent of this Success Criterion is to support people with low vision who need to enlarge text and read it in a single column. When the browser zoom is used to scale content to 400%, it reflows - i.e., it is presented in one column so that scrolling in more than one direction is not necessary.</p>
<p>It is important to avoid the need for users to scroll in the direction of reading in order to reveal lines that are cut off by the viewport. Such scrolling significantly increases the effort required to read. It is also important that the act of resizing content (zooming) does not cause some content to be hidden off-screen. For example, zooming into a vertically scrolling page should not cause content to be hidden to one side due to the page horizontal scrolling.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>It is important to avoid the need for users to scroll in the direction of reading in order to reveal lines that are cut off by the viewport. Such scrolling significantly increases the effort required to read. It is also important that the act of resizing content (zooming) does not cause some content to be hidden off-screen. For example, zooming into a vertically scrolling page should not cause content to be hidden to one side due to the page horizontal scrolling.</p>
<p>It is important to avoid the need for users to scroll repeatedly in the direction of reading a line of text, in order to reveal parts of lines that extend past the edge of the viewport. Such scrolling significantly increases the effort required to read. It is also important that the act of resizing content (zooming) does not cause content to extend outside the viewport in the direction of reading. For example, zooming into a vertically scrolling page should not cause content to fall outside the viewport to one side due to horizontal scrolling.</p>

This paragraph is about two-dimensional scrolling, so it should avoid phrases like "cut off" or "hidden" which sound more like loss of content.

s/scroll/scroll repeatedly/ because it would be fine for a single long line to need scrolling in the direction of reading, if the single line happens to be its own "section" of content.

<p>For people with low vision, both enlarging and reflowing text are critical to reading. Enlarging text enables the perception of characters. Reflowing text enables users to track from the end of one line to the beginning of the next line.</p>
<p>Avoiding the need to scroll in the direction of reading in order to reveal lines that are cut off by the viewport is important, because such scrolling significantly increases the effort required to read. It is also important that content is not hidden off-screen. For example, zooming into a vertically scrolling page should not cause content to be hidden to one side.</p>
<section>
Expand Down Expand Up @@ -58,6 +58,13 @@ <h3>Responsive web design and other ways to meet this Success Criterion</h3>
<h3>Avoiding scrolling in horizontally and vertically written languages</h3>
<p>The success Criterion applies to both horizontally and vertically written languages. Zooming the page for horizontally written languages where pages scroll vertically by default (e.g. English) should not require horizontal scrolling. Zooming the page for vertically written languages which scroll horizontally by default should not require vertical scrolling.</p>
</section>

<section>
<h3>Horizontally and vertically scrolling content</h3>
<p>Where a vertically scrolling page has sections of content which scroll horizontally (or the other way around), those sections would need to meet either the width/height bullet or the exception to pass this criterion.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>Where a vertically scrolling page has sections of content which scroll horizontally (or the other way around), those sections would need to meet either the width/height bullet or the exception to pass this criterion.</p>
<p>Where a vertically scrolling page has a [section](https://www.w3.org/TR/WCAG/#dfn-section) of content which scrolls horizontally, the section would need to meet either the "Horizontal scrolling content at a height..." bullet or the exception to pass this criterion. Where a horizontally scrolling page has a section of content which scrolls vertically, the section would need to meet either the "Vertically scrolling content at a width..." bullet or the exception to pass.</p>

"Section" needs explanation, or else I could call every sentence a "section" and badly defeat the intent. I suggest the normative "section". I'd be curious if there are other ways of explaining the intent of "section" that are even better suited to 1.4.10.

Here's my guess about what you meant by "the width/height bullet". Was this your intention?

<p>For example, in a vertically scrolling page, a horizontally scrolling section could be up to 256px tall, or meet the exception “require two-dimensional layout for usage or meaning”. In a horizontally scrolling page a vertically scrolling section could be up to 320px wide, or meet the exception.</p>
<p>Where part of the page meets the exception, or has scrolling within the size limit, it does not mean the rest of the content of page can also have scrolling. For example, a data table should use a wrapper element with horizontal scrolling, the rest of the page should not also scroll in 2 directions.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>Where part of the page meets the exception, or has scrolling within the size limit, it does not mean the rest of the content of page can also have scrolling. For example, a data table should use a wrapper element with horizontal scrolling, the rest of the page should not also scroll in 2 directions.</p>
<p>Where part of the page meets the exception, or has scrolling within the size limit, it does not mean the rest of the content of page can have two-dimensional scrolling. For example, in page which overall scrolls vertically, a data table can use a wrapper element with horizontal scrolling to prevent the rest of the page from scrolling horizontally.</p>

I suggest "can use" not "should use" so the recommendation does not preclude other good options, such as setting paragraphs outside the table to `max-width:100%".

</section>
<section>
<h3>The relation of Reflow to the Success Criterion 1.4.4 Resize Text</h3>
<p>The focus of the Reflow Success Criterion is to enable users to zoom in without having to scroll in two directions. <a href="resize-text" class="sc">Success Criterion 1.4.4 Resize Text</a> also applies, so it should be possible to increase the size of all text to at least 200% while simultaneously meeting the reflow requirement. For most implementations, the text is expected to continue to enlarge as the magnification increases, so that users can magnify text up to (and beyond) 400%. In an implementation where text does not consistently increase its size as people zoom in (such as when it is transformed based on a media query to adapt to small-screen usage), it must still be possible to get to 200% enlargement in order to satisfy the Resize Text criterion.</p>
Expand Down