E-mail List Archives
Re: SC 1.4.4: browser zoom and responsive design
From: Mallory
Date: Apr 12, 2017 12:17PM
- Next message: Sarah Ferguson: "good example of accessible schedules"
- Previous message: Fernand van Olphen: "Re: SC 1.4.4: browser zoom and responsive design"
- Next message in Thread: None
- Previous message in Thread: Fernand van Olphen: "Re: SC 1.4.4: browser zoom and responsive design"
- View all messages in this Thread
That's just basically "we think it's pretty when broken." I wish all
those
folks were forced to not be able to use a mouse and only get 9px light
grey text on white for all their computing for like a week at work.
cheers
On Wed, Apr 12, 2017, at 11:43 AM, Karl Brown wrote:
> 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.
> > >
> > >
- Next message: Sarah Ferguson: "good example of accessible schedules"
- Previous message: Fernand van Olphen: "Re: SC 1.4.4: browser zoom and responsive design"
- Next message in Thread: None
- Previous message in Thread: Fernand van Olphen: "Re: SC 1.4.4: browser zoom and responsive design"
- View all messages in this Thread