W3C home > Mailing lists > Public > public-web-and-tv@w3.org > March 2016

[Cloud Browser] My To-Do's

From: John Foliot <john.foliot@deque.com>
Date: Wed, 2 Mar 2016 10:22:35 -0600
To: <public-web-and-tv@w3.org>
Message-ID: <006801d1749f$bb69cbf0$323d63d0$@deque.com>
Hi all,


As discussed on today’s call, I’ve made some changes to the wiki:


Moved Terminology into a table to accommodate alternative names/terms for concepts being discussed: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Terminology


Added a new section to Use Cases for accessibility, and provided some backgrounder links there: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases#accessibility


Linked the Architecture page to the main Cloud Browser page (because it wasn’t there before):



I also mentioned Shadow DOM on the call today, and more details about that can be found at:


I’m not sure at this point whether this is relevant or not, but as explained, this concept was worked out to address accessibility requirements for the <canvas> element in HTML5, which essentially allowed the browser to ‘paint’ pixels to the screen (and animate them, both via JavaScript), but lacked any kind of scaffolding or framework that the Accessibility APIs could interact with. Shadow DOM addressed that problem, and is in production today. I’ve also added a link from Steve Faulkner that provides a primer on the accessibility tree requirements, as well as a link to the Core Accessibility API mappings – hope this helps.






John Foliot

Principal Accessibility Strategist

Austin, TX


Deque Systems Inc.
2121 Cooperative Way, Suite 210,  
Herndon, VA 20171-5344

Office: 703-225-0380 

 <mailto:john.foliot@deque.com> john.foliot@deque.com


Advancing the mission of digital accessibility and inclusion

Received on Wednesday, 2 March 2016 16:23:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:30 UTC