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: Patrick H. Lauke
Date: Jan 10, 2018 3:13AM

On 10/01/2018 10:05, Patrick H. Lauke wrote:
> On 10/01/2018 09:17, Mallory wrote:
>>> 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.
>
> That would also happen if they weren't using responsive web design. It's
> just bad design, period.

In fact, beyond a few tiny changes (the most visible one being that
dropping of text from the menu at <800px), www.twitter.com isn't really
a responsive site. The issue with the cut-off dropdown happens at all
sizes when the height of the browser window is less than the dropdown
length. Would also happen exactly the same way if you forced just
text-only resizing or similar. It's not intrinsically a "responsive web
/ full-page zoom" type problem, but yes a "just badly designed in
general" one.

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