W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2018

RE: responsive design and breakpoints and layout changes

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Thu, 4 Jan 2018 22:45:21 +0000
To: Phill Jenkins <pjenkins@us.ibm.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BN6PR03MB2513FC7B9C2EC7B2C452CB72F11F0@BN6PR03MB2513.namprd03.prod.outlook.com>
Interestingly I have a touch screen on my Windows 7 machine and with Chrome.  Zooming with the mouse wheel triggered the responsive design but pinch zooming added scrollbars.  So there is already some ability for this.   Generally with zoom and lower resolution we want responsive design - but we have all seen situations where zooming in actually causes some content to get smaller or doesn't enlarge as expected because what was set for each breakpoint.  A classic example of this is pinch zooming in a map to read the street names but when the map gets bigger the street names don't enlarge or sometimes even get smaller.


Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
(703) 637-8957
Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | LinkedIn<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/>
Looking to boost your accessibility knowledge? Check out our free webinars!<http://www.ssbbartgroup.com/webinars/>

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: Phill Jenkins [mailto:pjenkins@us.ibm.com]
Sent: Thursday, January 4, 2018 4:42 PM
To: w3c-wai-ig@w3.org
Subject: Re: responsive design and breakpoints and layout changes

Sounds like a User Agent/Browser issue, not something the web authors should be responsible for.

But I agree there should be some best practices and guidelines for accessibility with respect to responsive design - especially in the area of what the browser should be handling for them and guideloines for users on what to expect from the browsers.  For example, if the user zooms to 200%, do I get/want scroll bars or responsive design?  I just think it is more easily solved in the relatively few browser that trying to educate the thousands (millions?) of developers.  I agree it honestly seems like responsive design is the wild wild west where for many developers, all that matters is that it works for their eyes on the devices they happen to own - like guidelines and training are going to fix that . . .

Phill Jenkins
Check out the new system for requesting an IBM product Accessibility Conformance Report VPAT(r)at  able.ibm.com/request<https://able.ibm.com/request/>
Senior Engineer & Accessibility Executive
IBM Research Accessibility

From:        "Michael A. Peters" <mpeters@domblogger.net<mailto:mpeters@domblogger.net>>
To:        w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Date:        01/04/2018 02:54 PM
Subject:        responsive design and breakpoints and layout changes

In recent years, I frequently finding myself needing to increase the
size of web pages to see things on them.

On my desktop I often zoom to 120% and on my laptop to 140%.

This increases the number of physical pixels on the display relative to
the CSS pixels, and usually it works well.

Sometimes though it causes the design to change, responsive design,
which unfortunately then sometimes in a decrease in the size of images.

It's like they use 33% of the screen if X CSS pixels are available but
only 25% of the screen if less than X CSS pixels are available,
resulting in the opposite of what I want.

In my own playing, it seems like what they are likely doing is making
their responsive design relative to max-width rather than max-device-width.

It seems the former changes design relative to what CSS pixels are
available to the viewport to avoid side-scrolling at all cost, while the
latter sets the design to the device and if you zoom to the point where
side-scrolling is necessary, that's your choice that you have a reason
to do.

Obviously I prefer needing to side scroll from time to time if it means
I can adequately see the image, I don't want things like images to
shrink just because I tried to make them bigger.

Is anyone working on guidelines for accessibility with respect to
responsive design? It honestly seems like responsive design is the wild
wild west where for many developers, all that matters is that it works
for their eyes on the devices they happen to own.
Received on Thursday, 4 January 2018 22:45:53 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 4 January 2018 22:45:54 UTC