Guys please, move this to a different topic, this ARIA issue has now
clouded the original question.
David
--
David Dixon
t: 07967 569 489
e: [email protected]
linkedin | http://www.linkedin.com/in/davidjdixon
twitter | http://twitter.com/daviddixon
Matt Morgan-May wrote:
As someone who's on the working group producing ARIA, I have to say the
editors have done a pretty remarkable job in terms of documenting a
specification that hasn't even advanced past Working Draft.
First, there's the spec itself:
http://www.w3.org/TR/wai-aria/
Then there's the User Agent Implementation Guide, for browser developers to
follow:
http://www.w3.org/TR/wai-aria-implementation/
And the Best Practices Guide, for authors:
http://www.w3.org/TR/wai-aria-practices/
In addition, Steve Faulkner, also in the PFWG, has done lots of writing on
the subject:
http://www.paciellogroup.com/blog/?cat=23
And Universal Design for Web Applications, the book I co-wrote with Wendy
Chisholm, has a more basic introductory chapter on ARIA. The point is, it
may not all have a W3C banner at the top, but generally speaking, W3C is
more responsible for being complete and precise, than being prosaic. I
expect that the Web Standards Curriculum is most likely to have
author-friendly material on ARIA, and that's only when the spec is stable
enough for general consumption.
-
m
On 3/1/09 6:32 AM, "David Dixon" <[email protected]> wrote:
although the WAI ARIA team (as with the W3C in
general) need to start producing more palatable documentation rather
than just having huge technical manuals on the subject.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************
