- From: Matt King <a11ythinker@gmail.com>
- Date: Sat, 18 Nov 2017 09:53:29 -0800
- To: <public-aria-practices@w3.org>
- Message-ID: <004b01d36096$24eab9c0$6ec02d40$@gmail.com>
Team, Per our recent discussions, I have revised the section of the read me first about browser and assistive technology support to emphasize the need for interoperability testing before use in production. See: http://w3c.github.io/aria-practices/#browser_and_AT_support Please provide feedbac in review issue 529: https://github.com/w3c/aria-practices/issues/529 For your convenience, I pasted the new language below. 2.2 Browser and Assistive Technology Support Testing assistive technology interoperability is essential before using code from this guide in production. Because the purpose of this guide is to illustrate appropriate use of ARIA 1.1 as defined in the ARIA specification, the design patterns, reference examples, and sample code intentionally do not describe and implement coding techniques for working around problems caused by gaps in support for ARIA 1.1 in browsers and assistive technologies. It is thus advisable to test implementations thoroughly with each browser and assistive technology combination that is relevant within a target audience. Similarly, JavaScript and CSS in this guide is written to be compatible with the most recent version of Chrome, Firefox, Internet Explorer, and Safari at the time of writing. In particular, some JavaScript and CSS may not function correctly in Internet Explorer version 10 or earlier. Except in cases where the ARIA Working Group and other contributors have overlooked an error, examples in this guide that do not function well in a particular browser or with a specific assistive technology are demonstrating browser or assistive technology bugs. Browser and assistive technology developers can thus utilize code in this guide to help assess the quality of their support for ARIA 1.1. Best, Matt
Received on Saturday, 18 November 2017 17:53:59 UTC