search

w3c / wcag-eo

Repository for EO editorial work on WCAG
Other
4 stars 7 forks source link

Understanding 1.4.10 Reflow (Level AA) #1

Open nrhsinclair opened 6 years ago

nrhsinclair commented 6 years ago

Post suggested revisions to 1.4.10 here

nrhsinclair commented 6 years ago

Suggest the following revision to paragraph 3 for brevity, clarity and correction of typo: current: _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 signiicantly 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.__

revision: Eliminating the need to scroll in the direction of reading, significantly reduces the effort required to read and prevents content from being hidden off-screen.

sharronrush commented 6 years ago
sharronrush commented 6 years ago

In section "How reflow works," this sentence seems a bit confusing, since info is often theoretically "available" but requires horizontal scrolling.

Spatial relationships of content may change when users zoom, but all information and functionality should continue to be available.

Suggest replace "available" with "visible" or "available without horizontal scrolling."

sharronrush commented 6 years ago

In "Viewing distance..." section, change "What counts is not the absolute size of text..." to "More important than the absolute size of text is the relative size..."

a11ycob commented 6 years ago

I have quite a few changes and am attaching a Word doc with track changes, If that doesn't work for people let me know. reflow.docx

Amace41 commented 6 years ago

+1 to Chris' changes, agree a link about CSS pixels is a good idea. Also agree with Sharron's suggestion about "available without horizontal scrolling" Just one other quick suggestion. As I often use and hear the term 'Mobile Responsive', I suggest adding to the sentence: "Supporting the reflow of content is also known as 'Responsive Web Design'." and change it to "Supporting the reflow of content is also known as 'Responsive Web Design' or 'Mobile Responsive'"

vmmiller commented 6 years ago

@sharronrush : +1 > for the option "available without horizontal scrolling".

A suggestion for simplification of this paragraph is given below:

Current: User agents for technologies such as HTML/CSS, PDF, and ePub have methods for reflowing content to fit the width of the window (viewport). When appropriately authored, page content can reflow (wrap) to stay within the window's boundaries (viewport) when users zoom in to enlarge the size of content. Spatial relationships of content may change when users zoom, but all information and functionality should continue to be available.

Suggested change (with some input from @a11ycob (Chris)'s Word document):

Browsers (user agents) have methods for reflowing content such as html, PDF and ePub so that they fit the width of the window (viewport) with all content and functionality still being available. When properly authored, page content can reflow (or wrap) to remain within the window's boundaries. In this way, when users need to zoom in to enlarge the size of content, the content will remain within the window's boundaries without the need to scroll horizontally.

vmmiller commented 6 years ago

Paragraph 5, starting "Supporting the reflow of content..." Is the word "Importantly," necessary and can it be removed? In my view, it is superfluous.

vmmiller commented 6 years ago

Paragraph 6, very minor suggestions:

When we read online, the size of the print is not as important as the image it projects on the retina of our eye. Phones are designed for close viewing whereas desktops are designed for viewing farther away. As a consequence 16px print on a phone is physically smaller than 16px print on a desktop. This is not a problem because both print sizes cast the same image on our retina if they are viewed at their intended distance.

vmmiller commented 6 years ago

Paragraph 11, some minor suggestions. Current: "Content which requires two-dimensional layout for usage or meaning cannot reflow without losing meaning, and is therefore out of scope of this Success Criterion. For example, graphics and video are by their nature two-dimensional. Cutting up an image and stacking the blocks would render the content unusable so that is out of scope. However, it is possible to have these elements stay within the bounds of viewport at zoom levels to 400% (see advisory techniques)."

Suggested change: Content, which requires two-dimensional layout, cannot reflow without losing meaning, and is therefore out of scope of this Success Criterion. For example, graphics and video are by their nature two-dimensional. Cutting up an image and stacking the blocks would render the content unusable so that is out of scope. However, it is possible to have these elements stay within the boundaries of the viewport at zoom levels up to 400% (see advisory techniques).

vmmiller commented 6 years ago

Paragraph 12, minor suggestion. Current: ...This relationship is essential to convey the content.

Suggested change: ...This relationship is essential to convey meaningful content.

vmmiller commented 6 years ago

Paragraph starting "The layout method of.." Suggestion:

Current: The layout method of most common browsers in mobile operating systems does not offer reflow in the same way as on desktop browsers. In these browsers,...

Suggested change: The most common mobile browsers do not offer reflow in the same way as desktop browsers. In mobile browsers,

vmmiller commented 6 years ago

Suggestion: Merge the following paragraph with the previous one to emphasize the problem.

Current: The layout method of most common browsers in mobile operating systems does not offer reflow in the same way as on desktop browsers. In these browsers, content can be magnified in different ways, for example, by using a pinch gesture to scale up content, or a double tap on a particular column to make it fill the viewport width. This means that currently, mobile browsers usually exhibit horizontal scrolling regardless of what an author does.

In principle, mobile user agents can equally offer reflow when users zoom into content, as evidenced by the Dolphin browser for Android. The lack of reflow support in mobile operating systems can therefore be regarded as a user agent support issue.

Suggested change (with additional edits to compact the two paragraphs): The most common mobile browsers do not offer reflow in the same way as desktop browsers. In mobile browsers, content can be magnified in different ways, for example, by using a pinch gesture to scale up content, or a double tap on a particular column to make it fill the viewport width. Currently, mobile browsers often exhibit horizontal scrolling regardless of what an author does although, in principle, mobile browsers such as the Dolphin browser for Android have shown that they can equally offer reflow when users zoom into content. Therefore, the lack of reflow support in mobile operating systems can be regarded as a user agent support issue.