Re: Length of line & Resize & Reflow.

Hi David,

Thanks, I generally agree, I’m at busy-ness level “headless chicken” today, but in short:


-          That’s a good start, I’ll bring it up with LVTF this afternoon (all running well today);

-          We need to find a way to say that it is not something that devs need to provide a mechanism for in HTML. Having your block-level items in the right order and without preventing user-agent adjustments is the intended requirement.

-          Given that mechanism aspect, we don’t need the mobile exception.

-          The missing use-case I can think of is table cells within a table, and fitting the unit of content to the viewport. The solution/technique would be something like td, th {max-width: 100vw;}, but I’m not sure what the SC text for requiring that is.

I’ll come back to you more fully soon…

Cheers,

-Alastair


From: David MacDonald <david100@sympatico.ca>
Date: Thursday, 12 January 2017 at 01:13
To: Alastair Campbell <acampbell@nomensa.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Length of line & Resize & Reflow.

I originally thought 57 and 58 should be combined, but Wayne felt the table exception in 58 should not be an exception for 57... It would look like this.

A mechanism is available to view content as a single column, with blocks of text in this column user adjustable to maximum of 25 characters without increasing the text size in the user agent, and without requiring two dimensional scrolling, except where: * The content is in a data table which has more that one column. * The content contains interactive controls that that cannot be reflowed. * The user-agent does not provide a means of re-flowing content. * Reflow would cause distortion or loss of information [OR The spatial layout is essential to the function and understanding of the content.]




Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Wed, Jan 11, 2017 at 6:54 PM, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
JF wrote:
> I think we need to step back a bit; what is the real goal we are trying to achieve here? I don't think it has anything to do with actual character count (per-se), but rather that we need developers to not break text re-flow (perhaps to a minimum of 25 REMs - Root EMs<https://snook.ca/archives/html_and_css/font-size-with-rem>). Level-set: LVTF, is this the real "goal" here?

Sorry I'm late on this thread, travel & meetings and stuff, but John is correct - the goal was not to dictate a particular line length on everyone, but to enable manipulation for those people who need it.

I think we need an overview of how this group of SCs fit together, so people understand the intent, so we can improve the SCs without going in circles.

Overall:

1. Resize content [1], where a user would activate the browser-zoom functionality up to 400% of the default.
It is the *authors responsibility* to ensure that the CSS & media queries work to that level in normal circumstances.

2. Reflow to single column [2] is to enable people to go beyond 400% and have a correct reading order. It is NOT intended to be the authors responsibility to make the reflow happen (in HMTL), but to make sure that if someone does forcibly reflow the content, the reading order makes sense.

3. Line length [3] is to enable people to reduce the line length to something that fits within their vision, regardless of the sizing. Again, it is not intended to be the authors responsibility to make that line-length happen, but to ensure it works if people forcibly reduce the column width. That could be by window sizing, or a user-style sheet approach.

I'm not convinced that the Line length SC is needed if Reflow works, as the issues you'd get doing reflow are likely to be harder to deal with, but I haven't had much time on that Line length yet.

I also made a quick & rough media alternative to that explanation, a screencast:
https://alastairc.ac/tests/layouts/resizing-scs.mp4 (37MB video)

So there is no need to discuss whether a particular line-length is achievable at any zoom level, that was not the aim.

What would be good to discuss is how to refine the wording of the reflow & line length SCs to make that clear!

Cheers,

-Alastair

1] https://github.com/w3c/wcag21/issues/77

2] https://github.com/w3c/wcag21/issues/58

3] https://github.com/w3c/wcag21/issues/57