W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2016

Re: How 1.4.4 Resize text applies when mobile templates kick in

From: Michiel Bijl <michiel@agosto.nl>
Date: Wed, 2 Nov 2016 16:37:17 +0000
To: WAI IG <w3c-wai-ig@w3.org>
Message-Id: <9374C73D-E89B-403E-9AE3-BD7CB3C9D46B@agosto.nl>
+1, content should always be available.

If mobile users can do without the content it shouldn’t be on the website to begin with.

—Michiel

> On 2 Nov 2016, at 16:21, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> 
> On 02/11/2016 15:56, Beranek, Nicholas wrote:
>> Hey Matthew,
>> 
>> The SC description says it right there: “without loss of content or
>> functionality”. Therefore, if you zoom into the browser to 200%, you
>> would expect everything to still be there, albeit perhaps in a different
>> format.
>> 
>> With that, let’s think about possible solutions for when a user has a
>> lower resolution. One solution would be to detect if the user has zoomed
>> into the page. Unfortunately, there doesn’t appear to be a reliable
>> method of doing this. Detect-zoom got very close, but browsers have
>> modified how they handle zoom (e.g. Firefox changes the devicePixelRatio
>> value on manual zoom so you can’t differentiate between zoom mode and a
>> retina device). Here’s the library for more information:
>> https://github.com/tombigel/detect-zoom
>> 
>> 
>> 
>> We do the best we can. You can try Detect-zoom and see how well that
>> works out for you. You can also check the pixel ratio and set up CSS
>> media queries to account for that and try to sift out mobile devices.
> 
> Fundamentally, though, the problem is not "we can't accurately differentiate between mobile devices and users that zoom in on desktop", but rather "we shouldn't drop content/functionality based on viewport size", I'd say.
> 
> 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
> 
Received on Wednesday, 2 November 2016 16:37:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 November 2016 16:37:48 UTC