RE: Length of line

> "Linearisation: A mechanism is available to view content as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content".

Sailesh, the issue is that in non-responsive modes zoom creates horizontal scrolling.  Having to scroll left and right to read content that is scrolled off the screen is not effective and  problematic for users with low vision.

Jonathan

-----Original Message-----
From: Sailesh Panchang [mailto:sailesh.panchang@deque.com] 
Sent: Tuesday, February 07, 2017 2:04 PM
To: David MacDonald
Cc: Wayne Dick; Alastair Campbell; WCAG
Subject: Re: Length of line

Hello David,
Pardon if i am late to this discussion. I am trying to understand the rationale for this proposal:
"Linearisation: A mechanism is available to view content as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content".

I suppose this is based of
"Continuous Reading: Many people, with and without disabilities, find it more difficult to read when they must scroll from the bottom of a column of text to the top of another column". (See
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column)

If that's the reading-order expectation, is the content not marked up incorrectly? Everything in the first column should be in one TD or the content should be in DIVS positioned next to each other. If the content is presented in rows, I do not think the expectation is that one should read down one column and then start at the top of the next column.

I am assuming users who require significant magnification are using the necessary AT.
As one scrolls sideways say to the right, will the user not be accessing content only within the particular container / element like LI or TD or P or DIV etc.?
After that the content within the next LI or TD or P etc.  in the code order will be available to the user.

If all content on the page is properly marked up  so as to expose structure and semantics will that not be sufficient?
Maybe an extended version of SC 1.3.1 (atLevel AA) without the "or available in text" will suffice.

Or am I not grasping the issue?
Thanks,
Sailesh Panchang


On 2/4/17, David MacDonald <david100@sympatico.ca> wrote:
>>But it is still a relevant topic because Linearization (58) also has a
> similar exception though:
> “If the user agent cannot reflow content containing interactive 
> controls, the author is exempt from reflow with this content.”
>
> @Alestair
>
> Here's the current proposal for the first draft of WCAG 2.1. So 
> perhaps the issue you bring up is OBE, no?
>
> Linearisation: A mechanism is available to view content as a single 
> column, except for parts of the content where the spatial layout is 
> essential to the function and understanding of the content.
>
> Cheers,
> David MacDonald

Received on Tuesday, 7 February 2017 19:11:56 UTC