- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 6 Jul 2016 09:30:45 -0400
- To: Alastair Campbell <acampbell@nomensa.com>
- CC: Gregg Vanderheiden RTF <gregg@raisingthefloor.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <BLU436-SMTP230F95086584E62CA0CB577FE3A0@phx.gbl>
Hi Alastair you can write it up in the WIKI where the proposal is if you want... https://www.w3.org/WAI/GL/wiki/Possible_wording_from_Jason/David_for_LVTF_re:_zoom_without_horizontal_scroll You could out it in the background section under a heading of your choosing... Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 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 Wed, Jul 6, 2016 at 6:39 AM, Alastair Campbell <acampbell@nomensa.com> wrote: > Gregg wrote: > > *2) Alastair — yes we do use some terms like essential and “undermine the > purpose” in WCAG… Just pushing to see if we can get to it better. * > > > > AC: Ok, damn, it’s hard though. > > > > How about the last part is: “except for elements of the page where the > spatial layout *is required for* its use.” > > > > I don’t know how else to say that linearization would destroy the purpose > of the content/functionality. The definition of essential was pretty good > for that purpose; it is one of those ‘appropriate’ things that is not > automatable. > > > > Gregg wrote: > > *3) Alastair — yes a big problem is that we ONLY have pinch-zoom (Screen > zoom) on mobile. we should define what the other should look like and > send it in to accessibility@apple.com <accessibility@apple.com> and to > other mobile browser mfgrs Got an idea for a gesture for that? > (keyboard is usually CTR+ or CMD+ ) * > > > > AC: I think it needs to be a setting. You still need pinch-zoom for > non-responsive layouts and that is the mobile equivalent of cmd+. > > > > The issue is when a site sets the meta-viewport to device-width, then the > ‘layout sizing’ (pinch-zoom, the magnification style) means you cannot > reflow content. > > > > I would like a setting such as: “Pinch-zoom reflows for mobile-optimized > sites”. When ticked the pinch zoom works as it does now for non-responsive > sites, but on a responsive site it allows you to increase the size of > everything whilst re-flowing within the viewport. > > > > On a medium size device (e.g. tablet) that could trigger media queries > like on desktop, reflowing down to one column. Once you are on the smallest > media-query defined (usually the one-column ‘mobile view’) it just keeps > getting bigger and applies a max-width of 100% on everything. > > > > I’ve seen that done on a feed-reader I used to have, it’s definitely > possible (unfortunately the feed reader updated its behavior and doesn’t do > it any more). > > > > If people agree with that description, I can raise some bugs. > > > > > > *4) I like your three SIZINGS… are these standard or you take? * > > > > My take, I was trying to think of the least confusing way of defining > zooms! Going by the thing you are making bigger seems to help. (Going by > the user’s method of zoom is *very* confusing.) > > > > Is it worth me writing it up a bit more into a blog post or wiki page > somewhere? > > > > -Alastair > > >
Received on Wednesday, 6 July 2016 13:31:19 UTC