RE: Encouraging the use of technologies designed to support accessibility

I think it belongs on the issues list. I’m less concerned about when it’s addressed (i.e., for which WCAG version, whether 2.x or Silver).

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Friday, July 21, 2017 2:18 PM
To: David MacDonald <david100@sympatico.ca>; White, Jason J <jjwhite@ets.org>
Cc: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: Encouraging the use of technologies designed to support accessibility

This is a complete and total minefield. I suggest that we don’t try to get something like this into 2.1 because it will make supporting personalization seem like a cake walk.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk


From: David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>>
Date: Friday, July 21, 2017 at 14:12
To: "White, Jason J" <jjwhite@ets.org<mailto:jjwhite@ets.org>>
Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: Encouraging the use of technologies designed to support accessibility
Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Friday, July 21, 2017 at 14:12

I support this, it might clean up the crazy messing up of ARIA I see everywhere ... here's a rough wording for an SC.

****
When accessibility-enhancing Web technologies are used to increase the level of accessibility of a page they are used according to specification, unless they are used in a way that is otherwise accessibility supported.

****

Definition of accessibility-enhancing Web technology:


  *   Is used by user agents and assistive technologies to improve the accessibility of Web content.
  *   States explicitly in its specification that it is designed to improve accessibility for users with disabilities.
  *   Is designed to complement and to be compatible with the technologies that are used to implement the content (i.e., we aren’t requiring the author to change their implementation technologies).


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7C%7Cddd7e319b5e34011d14708d4d0642b79%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362576045684634&sdata=CGshV0Vv1jQ%2FguCzNXlVvvymesmXDB08jDw%2FBqq52iA%3D&reserved=0>

twitter.com/davidmacd<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7C%7Cddd7e319b5e34011d14708d4d0642b79%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362576045684634&sdata=YaVulnAxx7aWHlGYmU21d4lXywyPtjs3UDmZ2Yj89BE%3D&reserved=0>

GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7C%7Cddd7e319b5e34011d14708d4d0642b79%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362576045684634&sdata=FybkOjQlQ79NQJrZjYHSE3DCopkxrtDvp5VMWDFnYOw%3D&reserved=0>

www.Can-Adapt.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7C%7Cddd7e319b5e34011d14708d4d0642b79%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362576045684634&sdata=yFcj9HO9MQ56o8BgR%2Fr0s0I12vfd5PkNqqPc7pPdzi0%3D&reserved=0>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7C%7Cddd7e319b5e34011d14708d4d0642b79%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362576045684634&sdata=hmNZhppUkkZE6d3cHo5%2FlbdLFs1GrrF31OVONv5hRyE%3D&reserved=0>

On Fri, Jul 21, 2017 at 12:44 PM, White, Jason J <jjwhite@ets.org<mailto:jjwhite@ets.org>> wrote:
I think we should consider a carefully scoped proposal that in some circumstances requires the use of technologies which are specifically designed to enhance accessibility. We’re seeing several of these, including ARIA, the ARIA Digital Publishing module, work on an ARIA extension for SVG (currently stalled), and the COGA personalization proposals, as well as the Accessibility Object Model (i.e., an accessibility API for the Web platform).

Roughly, the idea is that accessibility-enhancing Web technologies should be used, and used according to specification, where an accessibility-enhancing Web technology is defined to be a technology that

  *   Is used by user agents and assistive technologies to improve the accessibility of Web content.
  *   States explicitly in its specification that it is designed to improve accessibility for users with disabilities.
  *   Is designed to complement and to be compatible with the technologies that are used to implement the content (i.e., we aren’t requiring the author to change their implementation technologies).
There may need to be an exception to address cases in which departure from specifications is necessary, and can be done in an interoperable fashion to work around bugs in user agents or assistive technologies.
Also, use of these technologies should only be required in circumstances in which their application makes sense, but it’s hard to define what those conditions are, as they vary for each of the relevant technologies. The specifications are likely to indicate what the technologies should be used for, however.
Thus I’m not sure whether this proposal can be made reliably testable. It’s much narrower than the WCAG 1.0 “use technologies according to specification” mandate, as it applies only to “accessibility-enhancing” technologies (markup languages, APIs, metadata formats, etc.). The “used according to specification” requirement is supposed to ensure that the technologies are used correctly and appropriately, in so far as these qualities are mandated by the specification.
In the “personalization” discussion today, the idea underlying this proposal attracted some interest, so I’m raising it here to enable others to consider wehther some version of it could be brought into shape for WCAG 2.1, for a subsequent 2.x release if there are any, or for Silver.


________________________________

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.

________________________________


________________________________

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.

________________________________