WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Making mobile view available to all as way of constraining a11y testing costs

for

From: Mallory
Date: Jan 10, 2018 2:17AM

>Do you have actual examples where this happens? Because it's not really
a given that responsive sites would cause more or less
cutoffs/overflowing, since every measure (be it a measure set in pixels,
or ems, or whatever) is scaled exactly the same way.

So Twitter goes responsive (text in menus turn into icons, the left-side thingie goes away) but if I want to log out, I need to zoom waaaaaay the hell out because they forgot that sticky headers with dropdown menus are poop. If my screen was as large as those Silicon-valley designers it probably would still fit but I'm on a Lenovo stinkpad, like 12" or something.

They check widths in their responsiveness but I guess they forgot about heights.

cheers,
Mallory

On Fri, Jan 5, 2018, at 12:18 AM, Patrick H. Lauke wrote:
> On 04/01/2018 23:05, Jonathan Avila wrote:
> >> This strategy is just a way of dealing with the reality that, in an auditing context, there are limited resources available for testing, and a seemingly growing number of breakpoints as the largest possible viewport size increases. What do you think?
> >
> > Because I use low resolution on desktop or some browser zoom I find myself almost always entering mobile breakpoints on my desktop . In my experience page zoom not only changes the viewport with but also the scale factor. So the text size of sites is different at a width of 533 then it would be by zooming to say 150% that gets me to 533 (number made up) but also has a scale factor of 1.5.
>
> I'm sure we've had this conversation many times before, but: using page
> zoom effectively changes how many physical/screen pixels make up a CSS
> pixel. So yes, full-page zoom will result in everything being bigger by
> that factor, and the reported viewport width being smaller by that same
> factor.
>
> > Thus there is a larger opportunity for non-fluid responsive sites to have issues such as text that is cutoff or overflows over other text or text over a different background without sufficient contrast.
>
> Do you have actual examples where this happens? Because it's not really
> a given that responsive sites would cause more or less
> cutoffs/overflowing, since every measure (be it a measure set in pixels,
> or ems, or whatever) is scaled exactly the same way.
>
> > A truly fluid site would not have these issues but in my experience most sites really aren't truly fluid but instead are a series of breakpoints.
>
> Do you have actual examples of a "truly fluid" site versus a "non-fluid
> responsive" site?
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > >