- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Wed, 23 Jul 2008 09:03:09 -0400
- To: "HTML WG" <public-html@w3.org>
- Cc: wai-liaison@w3.org
Hello HTML WG. I see by your Tracker that you have an ISSUE-35 on "aria processing." http://www.w3.org/html/wg/tracker/issues/35 The example of how to handle @longdesc in accessibility APIs (similarly to how @aria-describedby would be handled) is indeed something we will want your help in defining and likely want you to cover in your document(s). On the other hand, in some places the statement of this issue 35 seems over-broad. We are working on defining requirements on browser implementation of WAI-ARIA in our documents. (It's not all there yet.) These requirements are mostly host-language independent, but will include provisions that vary depending on the computing environment of the browser, particularly the profile of accessibility APIs that they choose to support. We have an issue 61 that will provide a reference point from which to find the requirements that we are defining so you don't have to re-invent those wheels. http://www.w3.org/WAI/PF/Group/track/issues/61 That itself is a Member-confidential link. By the time the browser requirements are ready for you to work with they will be in our publicly visible Editors' draft http://www.w3.org/WAI/PF/aria .. at the very least (if not on TR already -- that's up to you to decide what maturity you want to limit your input to). I trust you can find one of your company with Member access to trace through this issue URI to the public references, when the time comes that you are actively considering ISSUE-35. Al /chair, PFWG
Received on Wednesday, 23 July 2008 13:03:52 UTC