Let's rename #1
I think what was meant by that was, fleshing out what ARIA properties are
allowed on what HTML elements (finishing
http://hsivonen.iki.fi/aria-html5-bis/)
- Aaron
From:
"Anne van Kesteren" <annevk@opera.com>
To:
Aaron M Leventhal/Cambridge/IBM@IBMUS, Richard
Schwerdtfeger/Austin/IBM@IBMUS
Cc:
Alfred.S.Gilman@ieee.org, alice.liu@apple.com, "Beth Dakin"
<bdakin@apple.com>, "Michael Cooper" <cooper@w3.org>, hsivonen@iki.fi,
"James Craig" <jcraig@apple.com>, "Jonas Klink" <klink@google.com>,
marcsil@windows.microsoft.com, simonp@opera.com, "Tony Ross"
<tross@microsoft.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>
Date:
10/29/2008 11:22 PM
Subject:
Re: Need to discuss: normative spec for exposing ARIA via APIs
On Wed, 29 Oct 2008 15:13:41 -0700, Aaron M Leventhal
<aleventh@us.ibm.com> wrote:
> This part wasn't logged ... commitments to work on the various
> specs proposed:
> 1. HTML+ARIA to DOM API : commitment by Aaron Leventhal (IBM) and Jonas
> Klink (Google)
> 2. HTML DOM (with ARIA) to MSAA/IA2 : commitment by Aaron Leventhal
> (IBM) and Jonas Klink (Google)
> 3. HTML DOM (with ARIA) to ATK/ATSPI : commitment by Aaron Leventhal
> (IBM) and Jonas Klink (Google)
> 4. HTML DOM (with ARIA) to MSAA/UIA Express : no commitments yet
> 5. HTML DOM (with ARIA) to Mac OSXA : no commitments yet
>
> Any commitments to work on these specs from some other ARIA
implementors?
What came out of the informal ARIA discussion at TPAC was that it would be
good if there was a document that defines the abstract concept of the
"accessiblility tree" and how that maps to the various platforms APIs.
Then the HTML specification and the ARIA specification can define how
their semantics map to that "accessibility tree". (And SVG could do the
same later on.)
What exactly is HTML+ARIA to DOM API by the way?
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>