WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: SC 1.4.4: browser zoom and responsive design

for

From: Karl Brown
Date: Apr 12, 2017 3:43AM


Another reason zooming got disabled on some sites is because the UX/UI
designers or business insisted on it. I sat in a few meetings where it was
discussed "to keep the design looking as intended."

They didn't like it when I argued (UK based) about reasonable aids and
adaptations under the Equality Act 2010.

On Wed, Apr 12, 2017 at 10:21 AM, Mallory < <EMAIL REMOVED> > wrote:

> In case someone wonders why anyone *would* bother setting
> user-scalable to no... anyone who was using Hammer.js
> (a library with swipes and things built-in) did not work if users
> zoomed, so basically it was a requirement to set zooming off
> if your site used Hammer, and Hammer did have some popularity
> back when it was out.
>
> cheers,
>
> On Tue, Apr 11, 2017, at 03:10 PM, Tim Harshbarger wrote:
> > Another way to look at this might be...
> >
> > User interfaces are created with the intention of facilitating specific
> > user tasks. If it is still possible to perform those user tasks in an
> > accessible manner, then things are likely ok. If not, there is a problem.
> >
> > I think that is why it is important to have an understanding of the
> > author's intent when looking at the accessibility of a user interface. I
> > think one of our key goals is to ensure the author's intent is
> > communicated to users in as accessible a manner as possible--whether the
> > "author" intends just to communicate a piece of information or make it
> > possible for a user to buy a widget.
> >
> > When we don't know the author's intent, then we have to make assumptions.
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Karl Brown
> > Sent: Tuesday, April 11, 2017 5:56 AM
> > To: WebAIM Discussion List < <EMAIL REMOVED> >
> > Subject: Re: [WebAIM] SC 1.4.4: browser zoom and responsive design
> >
> > It comes down to whether it's the *functionality* that's important or the
> > *content*.
> >
> > The functionality is "the ability to see the collection dates", which the
> > list on mobile provides.
> >
> > If the calendar on desktop has additional functionality (quickly skip
> > through months, etc.) then mobile is missing functionality. Otherwise I'd
> > argue that the core purpose, the dates, are still available in a readable
> > format so don't need to be shown the same way where doing so would impair
> > understanding.
> >
> > On Mon, Apr 10, 2017 at 7:11 PM, Jonathan Avila
> > < <EMAIL REMOVED> >
> > wrote:
> >
> > > > The responsive design in my example misses functionality that the
> > > desktop design does have.
> > >
> > > If there is no way to get to the functionality it seems like an issue
> to
> > > me. In some cases there is a link to a desktop site and that would
> allow
> > > the user to access the content in a none-responsive way and use pinch
> zoom.
> > >
> > > Jonathan
> > >
> > >
> > > -----Original Message-----
> > > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > > Behalf Of Fernand van Olphen
> > > Sent: Sunday, April 09, 2017 5:06 PM
> > > To: <EMAIL REMOVED>
> > > Subject: [WebAIM] SC 1.4.4: browser zoom and responsive design
> > >
> > > With interest I have followed the discussion about SC 1.4.4, resize
> text.
> > > Conclusion: browser zoom is allowed.
> > >
> > > My question is about browser zoom and responsive design.
> > >
> > > Suppose I visit a website. It is a garbage-day calender. It gives me
> the
> > > option to browse through the months to check when my garbage is
> collected.
> > > After a few zooms the responsive design kicks in. In this design the
> > > calender is replaced by a static list without the option to browse
> through
> > > the months. In other words: the responsive design does not give me the
> same
> > > options as the desktop design does.
> > >
> > > https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G142 says under
> > > Tests > procedure:
> > >
> > > 1. Display content in a user agent
> > >
> > > 2. Zoom content to 200%
> > >
> > > 3. Check whether all content and functionality is available
> > >
> > > The responsive design in my example misses functionality that the
> desktop
> > > design does have.
> > >
> > > Is this a violation of SC 1.4.4?
> > >
> > > Kind regards,
> > > Fernand van Olphen
> > > Accessibility Advisor
> > > Municipality of The Hague
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u
> > > op: http://www.denhaag.nl/disclaimer > > > _________________
> > > > archives
> > > at http://webaim.org/discussion/archives
> > > > > > > > > > > > > > > > > >
> >
> >
> >
> > --
> > Karl Brown
> > Twitter: @kbdevelops
> > Skype: kbdevelopment
> >
> > Professional Certificate Web Accessibility Compliance (Distinction),
> > University of South Australia, 2015
> > > > > > > > > > > > > > > > > > > > >



--
Karl Brown
Twitter: @kbdevelops
Skype: kbdevelopment

Professional Certificate Web Accessibility Compliance (Distinction),
University of South Australia, 2015