W3C home > Mailing lists > Public > public-html-a11y@w3.org > May 2011

[Bug 10919] Allow role="presentation" to override the default role of any element

From: <bugzilla@jessica.w3.org>
Date: Wed, 18 May 2011 13:24:53 +0000
To: public-html-a11y@w3.org
Message-Id: <E1QMgk9-0005cF-5v@jessica.w3.org>

--- Comment #18 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-05-18 13:24:51 UTC ---
(In reply to comment #17)
> For <a href role=presentation>, IIRC ARIA requires role=presentation to be
> ignored for focusable elements (you have to expose the element for it to be
> focusable). I don't know if ARIA bans role=presentation for focusable elements
> for document conformance, but it probably should.

James Craig touched this:

His quote from ARIA: ''If an element with a role of presentation is focusable,
user agents MUST ignore the normal effect of the role and expose the element
with implicit native semantics, in order to ensure that the element is both
understandable and operable. ''

I did indeed not think about this when I suggested to use <a role=presentation
href=link >. 

HOWEVER, it is possible that ARIA should continue to permit role=presentation
on focusable elements, because:

* the ARIA spec text talks about 'the *normal* effect of the role'. For
example, what if a table cell of a presentational table has the tabindex
attribute set? It would be meaningless to treat that table cell as a
non-presentational table cell.

* note also that @role may take a list of several roles. I would thus suggest
 <a role=presentation href=link > is equal to 
 <a role='presentation link' href=link>

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 18 May 2011 13:24:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:56 UTC