W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2008

Comments on UAAG 2.0 requirements

From: Aaron Leventhal <aaronlev@moonset.net>
Date: Fri, 18 Apr 2008 10:32:23 +0200
Message-ID: <48085C97.4050305@moonset.net>
To: "'WAI-ua'" <w3c-wai-ua@w3.org>


I'd like to see more mention of ARIA and HTML 5. There is a lot 
happening there.

What would be useful to me would be exact guidelines as to how to expose 
these things via various a11y APIs. I have no idea how to expose content 
to Universal Access. However, I can help provide info on how to expose 
to ATK/AT-SPI or MSAA/IAccessible2. ATs can't rely on the DOM alone -- 
layout info is necessary.

The next thing that would be useful would be test cases and automated 
tests that check browsers to see if they expose content to these APIs 
the same way.

This API stuff is 75% of the work we have to do to make Firefox 
accessible. Can the UAWG say how much it can commit to be involved in 
coordinating with the community on this, defining correct mappings and 
testing them? Does UAWG consider itself the right place to deal with 
these platform specifics in such detail?

I'd like to see docs like this but for HTML etc.:

- Aaron
Received on Friday, 18 April 2008 08:33:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:38 UTC