- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 15 Jul 2016 14:10:11 +0000
- To: Kurt Mattes <kurt.mattes@deque.com>, "Patrick H. Lauke" <redux@splintered.co.uk>
- CC: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <BY2PR0701MB1990F854EDE091379623AC7EAB330@BY2PR0701MB1990.namprd07.prod.outlook.>
From: Kurt Mattes [mailto:kurt.mattes@deque.com] Sent: Friday, July 15, 2016 9:01 AM In my roughly 15 years of experience, when undefined words like "mainstream" appear in WCAG, the opportunity for distracting debate is created at the point when people are trying to apply WCAG. One word in WCAG can disrupt and derail efforts that were otherwise successfully proceeding with the usual level of resistance. On the other hand, the authors of WCAG are trying to be mindful of the critically important need to avoid requiring content authors to support every and any AT or user agent. The WCAG Conformance language uses the defined term "relied upon'. Perhaps substituting "relied upon" for "mainstream" would avoid the possibility for debate while preserving the need to avoid requiring support for everything. That said, if the new exotic AT conforms to UAAG, perhaps a need to code specifically for it would not exist, nullifying the need to qualify AT with "mainstream". If UAAG conformance does not exist, then the lack of accessibility falls to the AT, not on the WCAG conforming authored content. [Jason] This is a fundamentally important observation. The type of assistive technology under consideration could be regarded as satisfying the following requirements. 1. It is available to the public (whether for free or on a commercial basis). 2. It supports relevant standards so that the content author need not specifically support it with measures not required by other standards-conformant AT. Such definitions are much more valuable and specific than words such as “mainstream”. ________________________________ 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 Friday, 15 July 2016 14:10:42 UTC