W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

Re: viewport/browser window size does not imply presence/lack of touch input...

From: Detlev Fischer (TK) <detlev.fischer@testkreis.de>
Date: Wed, 17 Jan 2018 10:23:09 +0100
To: w3c-wai-gl@w3.org
Message-ID: <68892d9c-cd88-63b4-2767-b58e6b6489e0@testkreis.de>
Hi Patrick,

I guess you meant to say

"UNLESS the user has a mechanism to zoom, the following must be true"

...or (which is the same thing essentially)

"IF the user doesn't have a mechanism to zoom, the following must be true"


I think adding this exception would largely pull the rug from under this 
SC since nearly all UA (or mobile OS, in their accessibility settings) 
allow some form of zoom - so you would have a SC which you can in most 
cases ignore (or which would have as only technique for authors 
something like "Do not prevent the user from zooming by setting meta 
name=viewport maximum-scale=1", or similar).


Am 16.01.2018 um 22:57 schrieb Patrick H. Lauke:
> On 16/01/2018 20:38, David MacDonald wrote:
> [...]
>>> Also, what about zooming? It's a mechanism that allows users to make 
>>> things (including target sizes) bigger, and it's built into most 
>>> (all?) current browsers...
>> I don't think so, its not changing CSS pixels, is it?
> However, it addresses the actual issue the SC is trying to address - 
> it makes target size as big as the user wants/needs to actuate it 
> comfortably. So perhaps it needs to be set as an exception/exclusion 
> for the overall SC - UNLESS the user doesn't have a mechanism to zoom, 
> the following must be true...
> P

Detlev Fischer PhD

Telefon: +49-40-43 18 75-25
Mobile: +49-157 57 57 57 45
Fax: +49-40-43 18 75-45
E-Mail: detlev.fischer@testkreis.de

Anschrift: Werderstr. 34, 20166 Hamburg
Amtsgericht Hamburg HRB 58 167
Received on Wednesday, 17 January 2018 09:24:13 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:21 UTC