- From: David MacDonald <david@can-adapt.com>
- Date: Wed, 5 Sep 2018 10:48:54 -0400
- To: Jonathan Avila <jon.avila@levelaccess.com>
- Cc: Alastair Campbell <acampbell@nomensa.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAAdDpDa3=FdgWUtdfrAGY7nDKUBM9XsY458LOTNb=cqODvaNsQ@mail.gmail.com>
It's an interesting perspective that it won't be 2 direction scrolling if its not more than the viewports height, and the SC is a content based SC rather than page based. I don't remember discussion distinguishing content from a web page for the purposes of this SC. Perhaps that is something that happened on the TF, it appears that Jonathan doesn't recognize that discussion either and he was on the LVTF? However, there is a natural distinction between the content and a web page that might be used to justify this position, content (Web content) information and sensory experience to be communicated to the user by means of a user agent <https://www.w3.org/TR/WCAG21/#dfn-user-agents>, including code or markup that defines the content's structure <https://www.w3.org/TR/WCAG21/#dfn-structure>, presentation <https://www.w3.org/TR/WCAG21/#dfn-presentation>, and interactions Web page a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent <https://www.w3.org/TR/WCAG21/#dfn-user-agents> Perhaps an author can squiggle through with a small amount of horizontally scrolling content (that doesn't require vertical scrolling) with that justification, but I don't think that is the intention of the SC. I think the intention is that western users should not have to horizontal scroll and Eastern LV users shouldn't have to vertically scroll. It is vertically scrolling page (Western languages) and adding horizontal for one paragraph would be 2 directions of scrolling so the only exception I can see in the SC is "Except for parts of the content which require two-dimensional layout for usage or meaning." I would as if its necessary to horizontally scroll, and if not wrap it. However, if a client was in court and I was trying to defend them, I'd use your rational. Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Mobile: 613.806.9005 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> 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 Tue, Sep 4, 2018 at 1:00 PM Jonathan Avila <jon.avila@levelaccess.com> wrote: > My thought is whether it is essential? A short English paragraph could > scroll horizontally and I sometimes see this one part of a page scroll but > other parts do not. One horizontally scrolling paragraph scrolling in > English remains a problem for the reflow SC in my opinion. > > > > However, I understand that there are some controls like carousels that > display multiple items on-screen at once that allow you to scroll > horizontally – like those used for video and game titles on streaming > services. In this case the individual pieces fit on the screen but the > control as a whole scrolls additional content horizontally. This seems > like it fits in the essential exception. > > > > Jonathan > > > > *From:* Alastair Campbell <acampbell@nomensa.com> > *Sent:* Tuesday, September 4, 2018 12:47 PM > *To:* David MacDonald <david@can-adapt.com> > *Cc:* WCAG list <w3c-wai-gl@w3.org> > *Subject:* Horizontal scrolling & reflow > > > > Hi David, > > > > We had a little side-bar on a call around reflow & horizontal scrolling. > > > > The context was whether you can have a horizontally scrolling nav-bar in > an otherwise vertically scrolling page. > > > > I’m struggling to find an example now, the client instance is pre-live, > the other instance I could think of was theguardian.co.uk, but they’ve > changed it now (I wonder why). > > > > Oh, I found it using the wayback machine, look at the top nav on here: > > https://web.archive.org/web/20150630123506/http://www.theguardian.com/uk > <https://web.archive.org/web/20150630123506/http:/www.theguardian.com/uk> > > > > If you have a touch-pad, that bit of content scrolls horizontally. > > > > My read of the Reflow SC is that it applies to ‘content’, rather than > pages (which was intentional): > > Content can be presented without loss of information or functionality, and > without requiring scrolling in two dimensions for: > > > > - Vertical scrolling content at a width equivalent to 320 CSS pixels; > > · Horizontal scrolling content at a height equivalent to 256 CSS > pixels. > > > > I.e. if a bit of a page scrolls horizontally, that’s ok if it fits within > 256px high. However, if that same bit of content requires scrolling in both > directions, it fails that SC. > > > > That bit of content does not require scrolling vertically, but does > horizontally. > > > > The same will apply on Korean / Japanese pages with a mix of vertical and > horizontally read text-blocks. (I say “will” because it is only really > becoming possible to do in browsers natively quite recently.) > > > > For those mixed-content pages you would zoom in and blocks would reflow, > but some of them could scroll vertically, and some horizontally. > > > > Does that make sense? > > > > Kind regards, > > > > -Alastair > > > > -- > > > > www.nomensa.com / @alastc > > >
Received on Wednesday, 5 September 2018 14:49:28 UTC