- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 23 Oct 2009 00:26:41 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, david.bolter@gmail.com
- CC: Jonas Sicking <jonas@sicking.cc>, Lars Gunther <gunther@keryx.se>, Shelley Powers <shelley.just@gmail.com>, HTMLWG WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Tab Atkins Jr. On 09-10-22 17.51: > On Thu, Oct 22, 2009 at 10:18 AM, Leif Halvard Silli: >> I don't know if a handful of pages can be used to formed an opinion. But if >> we had info about a handful of UAs that support ARIA, about whether they >> always let ARIA over-rule the default semantics, then that would definitely >> be helpful. > > A handful? That's half a million. You said: "Scanning the list, you find only a handful of uses which are ARIA-related," [...] >> I think simple rules are better. Why don't you agree? [...] > In this case, though, the route that HTML5 takes - "You're allowed to > use ARIA according to this table." - is relatively simple too. But I think authors will experience - due to how *ARIA* is specified - that ARIA is respected by UAs, regardless of whether it is valid. See what David said: David Bolter On 09-10-22 17.44: [...] > http://www.w3.org/WAI/PF/aria-implementation/#mapping_role > > ARIA roles override the implicit host language roles unless there is no > good mapping from the ARIA role to the desktop accessibility API. > > Firefox currently respects ARIA roles where supplied, and falls back to > host language mappings where necessary. -- leif halvard silli
Received on Thursday, 22 October 2009 22:27:17 UTC