- From: Leonard Rosenthol <lrosenth@adobe.com>
- Date: Sun, 12 Sep 2010 09:39:30 -0700
- To: "'Tab Atkins Jr.'" <jackalmage@gmail.com>, Steven Faulkner <faulkner.steve@gmail.com>
- CC: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, Maciej Stachowiak <mjs@apple.com>
>UAs can do whatever they want to communicate the >element's meaning to the user, if their accessibility APIs are richer >than what is exposed by ARIA. > FWIW, the PDF/UA (ISO 14289) committee took a similar position, in that there may/will be a disconnect between what a given UA (or conforming reader, in their parlance) supports and what a given OS provides for accessibility APIs - or even between available accessibility APIs (eg. MSAA vs. IAccessible) Leonard
Received on Sunday, 12 September 2010 16:40:26 UTC