Reading through the documents... > Authors are not responsible for the browser or assistive technology If authors make their own method based hanging off a catch all method at the end of list of methods for a guideline, I suggest they should have an obligation to demonstrate that the work with current Assistive tech and Browsers rather than a theoretical "it should work" basis (i.e. aria-errormessage should work but its not supported yet). I would call this "Ensuring new methods (not already listed in the spec) are Accessibility Supported". Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613-806-9005 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Fri, Dec 14, 2018 at 10:06 AM Jeanne Spellman < jspellman@spellmanconsulting.com> wrote: > agenda+ Point system/Levels & Conformance document > > https://docs.google.com/document/d/1wTJme7ZhhtzyWBxI8oMXzl7i4QHW7aDHRYTKXKELPcY/edit#heading=h.xzxmbeyrlvz7 > > agenda+ Heuristics proposal > > https://docs.google.com/document/d/1lEkht-bhkaPMzOojWpDjZhbnGeckiYLh-J4-ze7cGS0/edit#heading=h.dge8hcv9s32m > > agenda+ Updates from other prototypes > > ==Conference Call info== > > https://www.w3.org/2017/08/telecon-info_silver-fri > > >Received on Monday, 17 December 2018 18:44:09 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:23:57 UTC