W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > April 2017

RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?

From: White, Jason J <jjwhite@ets.org>
Date: Mon, 24 Apr 2017 22:19:44 +0000
To: Alastair Campbell <acampbell@nomensa.com>
CC: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-ID: <BN6PR07MB34571CDC591901A741411163AB1F0@BN6PR07MB3457.namprd07.prod.outlook.com>


> -----Original Message-----
> From: Alastair Campbell [mailto:acampbell@nomensa.com]
> Sent: Monday, April 24, 2017 5:37 PM
> 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.

[Jason] I think that's true in general, but when all of the non-working UAs happen to be the mobile versions, and when the working ones aren't, it somewhat curtails the user's opportunities.
>
> 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.
>
[Jason] I'm finding it hard to separate those issues in this case. What is it about an underlying format that would prevent the Adapting Text requirements from being supported, even if they aren't already? Rasterized images, to be sure, won't support it (I'm taking it that OCR/document recognition  isn't a viable mechanism in that case), but nobody is proposing to use a raster image format by itself to conform to WCAG.
 If we take the contingent facts about what user agents currently support out of consideration for the moment, then it seems to me that any format or combination of formats that have a chance of being used to conform to WCAG in other ways can meet the Adapting Text requirements, even if it entails adding new user agent features.
Thus it ultimately isn't, in practice, a question about the content formats.

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________
Received on Monday, 24 April 2017 22:20:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:35 UTC