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 12:54:59 +0000
To: Laura Carlson <laura.lee.carlson@gmail.com>, Gregg C Vanderheiden <greggvan@umd.edu>
CC: Alastair Campbell <acampbell@nomensa.com>, Andrew Kirkpatrick <akirkpat@adobe.com>, Joshue O Connor <josh@interaccess.ie>, Stephen Repsher <stephen.j.repsher@boeing.com>, To Henry <shawn@w3.org>, Jim Allan <jimallan@tsbvi.edu>, Glenda Sims <glenda.sims@deque.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-ID: <BN6PR07MB3457670498453240879726E8AB1F0@BN6PR07MB3457.namprd07.prod.outlook.com>


> -----Original Message-----
> From: Laura Carlson [mailto:laura.lee.carlson@gmail.com]
> This gets us back to the question Alastair previously asked [7], "Can we define
> those for 2017? HTML etc., yes. PDF, yes. What else would you call a 'major web
> technology' today?"
[Jason] HTML 5, CSS, JavaScript, SVG, PDF and various media formats cover almost everything that I've encountered in recent years.
Some educational simulations use WebGL, but it can't meet WCAG by itself and needs to be complemented with HTML for that purpose.
I think it's reasonable for us to say that some technologies simply can't be used to conform to WCAG 2.1, and to recognize that a lot of older content just won't be updated to meet WCAG 2.1 anyway.


________________________________

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 12:55:35 UTC

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