Re: 1.4.10 Reflow and mobile user agents

Hi Detlev,

This came up before and was discussed quite a lot, that's where the 1st FAQ came from, particularly:
"The main principle here is that the web content must be capable of resizing. It is not a device-specific issue."

Theoretically all of the SCs should be testable without using a particular user-agent, even the orientation & gesture ones. (That may not be practical right now, but we should be able to identify specific CSS/JavasScript that would trigger failures regardless of having a mobile device.)

In practice testers will need a desktop (style) browser to test 1.4.10, but it is a test of the content at a specific width, rather than needing a desktop-browser per-se.

That was also one of the good reasons to keep 1.4.4 (not that we could get rid of it anyway), as the 200% + scrolling still applies to mobile (style) devices. I.e. don’t prevent users from pinch-zooming.

-Alastair


On 01/05/2018, 12:08, "Detlev Fischer" <detlev.fischer@testkreis.de> wrote:

    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…
    Detlev

Received on Tuesday, 1 May 2018 11:32:38 UTC