- From: Janina Sajka <janina@rednote.net> (janina@rednote.net) <janina@rednote.net>
- Date: Thu, 20 Sep 2012 15:28:09 -0400
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
I'm looking at the independent stacks criterion for CR exit and want to ask about it in a11y related real world terms ... 1.) We have cross platform user agents, e.g. Firefox available for Windows, Android, Linux, etc. Are these separate stacks? Or one stack? How do we know for sure, i.e. the actual UI code is pretty different on each OS, is it not? Certainly, the assistive technology involved is different. On the other hand, the point of a cross-platform app like Firefox is to reuse code as much as possible. 2.) Are AT-SPI/ATK and IAccessible2 one stack or two? The latter is a derivative of the former implemented in a separate OS. The AAPIs look very similar, however. 3.) What about KDE and GNOME on Linux/Unix? Two stacks or one? For accessibility both use AT-SPI, though KDE does not use ATK in order to talk to AT-SPI. The browser will clearly be different, yet the AT may be the same for KDE and GNOME browsers, because of the common AT-SPI layer (which is designed to support AT interoperability among toolkits). Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net The Linux Foundation Chair, Open Accessibility: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/
Received on Thursday, 20 September 2012 19:28:33 UTC