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

RE: 1.4.10 Reflow and mobile user agents

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Tue, 1 May 2018 11:23:38 +0000
To: Detlev Fischer <detlev.fischer@testkreis.de>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <BN6PR03MB2513BFE8820E34737FC88738F1810@BN6PR03MB2513.namprd03.prod.outlook.com>
Hi Detlev,

It is my understanding that 1.4.10 is about presenting content at 320 CSS pixels and not whether the text actually becomes zoomed or not.  So 320 CSS presentation should be supported on mobile just fine even if the text size doesn't increase.  That is why we also have SC 1.4.4.     So this applies to mobile but the benefits on mobile aren't as great to the user as they are on the desktop.


-----Original Message-----
From: Detlev Fischer <detlev.fischer@testkreis.de> 
Sent: Tuesday, May 1, 2018 7:06 AM
To: WCAG <w3c-wai-gl@w3.org>
Subject: 1.4.10 Reflow and mobile user agents

As I am trying to edit the Understanding text of 1.4.10 Reflow, I am wondering whether to lack of mobile user agents that offer reflow (apart from the Dolphin browser on Android, maybe some others) means that WCAG 2.1 as a whole can only ever be met for a desktop-oriented accessibility baseline?
If authors want to claim conformance to WCAG 2.1 also on mobile devices, is there a need for a particular exception or a particular statement saying that

- 1.4.10 does not apply to mobile UA; or
- can in principle be met on mobile OSs, as evidenced by the Dolphin browser for Android, so this.is a UA issue;
- 1.4.10 is implicitly met by other broadly equivalent means, e.g. the double tap gesture to zoom-in to selected columns (this means you can selectively zoom in and out of content without having to scroll)
- something else?

Not sure how to handle this…
Received on Tuesday, 1 May 2018 11:24:07 UTC

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