- From: Aaron M Leventhal <aleventh@us.ibm.com>
- Date: Wed, 5 Nov 2008 09:50:38 -0500
- To: "wai-xtech@w3.org" <wai-xtech@w3.org>
- Cc: mick@kulgan.net, jamie@jantrid.net
Received on Wednesday, 5 November 2008 14:52:19 UTC
On 11/5/2008 1:20 AM, James Teh wrote: Hi all, It's probably too late to reconsider this now, but I'm curious nevertheless: Why was it decided to specify ARIA landmarks using ARIA roles? This does not seem logical to me: * The role of an element usually indicates its behaviour and how it should be treated. * Landmarks, on the other hand, provide structural information. They do not indicate the behaviour of an element. For example, whether an element is a navigation landmark does not affect how it should be handled by an AT; it is just a way of easily finding the element. * I think it would be more logical to specify landmarks in a separate attribute. * Landmarks are generally (always?) handled differently to normal roles by ATs. This in itself indicates that role is perhaps not the best representation. See also this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=459395 Thoughts greatly appreciated.
Received on Wednesday, 5 November 2008 14:52:19 UTC