- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 24 Apr 2017 21:37:14 +0000
- To: "White, Jason J" <jjwhite@ets.org>
- CC: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
> [Jason] One of the issues in the current discussion which isn't addressed by the definition of "accessibility supported" in WCAG, is that certain accessibility-related features may not be supported at all in some environments (e.g., on mobile devices, as in Adapting Text and Resize Content, if I understand the issue correctly). I thought we had covered that previously: The content needs to be what is assessed as passing, not whether it works across all UAs. Of course it does need to work on multiple UAs, and be (relatively) easily tested, but it doesn't have to work across all UAs. NB: Adapting text can work in a similar fashion on mobile devices (via bookmarklet and built in features like 'reader' in Safari). Resize content doesn't work in the same way on mobile, but it is the re-sizing for mobile that enables it to work on desktop browsers. However, this is a separate issue from the current thread on whether to use technology/mechanism text in the adapting text SC, which is about the underlying format, not the user-agent. Cheers, -Alastair
Received on Monday, 24 April 2017 21:37:50 UTC