W3C home > Mailing lists > Public > public-html@w3.org > September 2010

Re: ARIA mapping status

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Thu, 9 Sep 2010 16:23:45 +0100
Cc: 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>
Message-Id: <A1F6CEBE-E7EC-4DA5-AB38-3911E191E577@googlemail.com>
To: Steven Faulkner <faulkner.steve@gmail.com>
On 9 Sep 2010, at 15:50, Steven Faulkner wrote:
> One of  the factors that lead me to file the bug was the mandating of default roles that I disagree with, and also the incomplete implementaion advice that the ARIA role mapping provides

Providing additional informative guidance would not change conformance requirements ("mandating of default roles").

> what is so problematic with providing detailed html element to accessibility API mapping advice in the HTML5 spec anyway?

Perhaps a W3C staff member will correct me if I'm wrong, but I suspect a W3C Note would allow inline updates whereas we can only add errata to a Recommendation. As we are very likely to want to update API mapping advice for HTML5 as implementing platforms and available AT change, and as presenting information inline is clearer for readers, it would be best to use a Note.

I believe this is why WAI guidelines typically use Recommendations for platform-independent standards (WCAG, ATAG, UAAG, ARIA) and Notes for implementation advice (e.g. WCAG Techniques, ARIA Implementor's Guide).

--
Benjamin Hawkes-Lewis
Received on Thursday, 9 September 2010 15:24:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC