W3C home > Mailing lists > Public > public-silver@w3.org > January 2019

RE: Prohibiting authors from disabling Pinch Zoom as failure for Reflow 1.4.10

From: Alastair Campbell <acampbell@nomensa.com>
Date: Wed, 30 Jan 2019 18:21:33 +0000
To: Silver TF <public-silver@w3.org>
Message-ID: <AM5PR0902MB200281A2D0D0CBA26B668EEEB9900@AM5PR0902MB2002.eurprd09.prod.outlook.com>
Luis wrote:
> I would say, it's still a failure and that the responsibility is with the site developer.

This is a key thing to be able to say via conformance: This is the level of responsibility for the website developer/designer/owner.

Shawn wrote:
> Given our current direction of only having methods and not having "Failure techniques", I think this example would pass, as the user has ways to still zoom as needed, given that a cognitive walkthrough would take into account the user agent ability to override the zoom behavior of the site (just like user stylesheets can override site CSS).

I suspect this would be a lot easier to do if the guidelines were oriented around user-requirements, e.g. “Users can increase the size of content”, with user-agents methods (having a zoom feature) and website methods (e.g. don’t disable pinch-zoom, use media queries).

In that way you can construct the conformance with a mix of assumptions about user’s technology, and things the website must do to also support that.

However, it doesn’t remove the need to have some sort of ‘accessibility supported’ concept, or a set of methods known to be supported in general at the time of publication.



PS. I suspect the option isn’t in Chrome/iOS because Safari (and its engine that Chrome has to use on iOS) doesn’t respect that meta-viewport restriction any more.
Received on Wednesday, 30 January 2019 18:21:58 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:44 UTC