[Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default

https://www.w3.org/Bugs/Public/show_bug.cgi?id=11557

--- Comment #42 from steve faulkner <faulkner.steve@gmail.com> 2012-03-13 09:42:46 UTC ---
(In reply to comment #41)
> (In reply to comment #40)
> > (In reply to comment #33)
> > > <button role=button aria-pressed=true> should not do anything different than
> > > <button aria-pressed=true> according to the ARIA spec as far as I can tell
> > > (that's what the "implicit semantics" stuff is all about!). If it does, ARIA
> > > should be fixed.
> > 
> > Ian, you're misunderstanding the role of ARIA in the DOM. Redundant ARIA is
> > really helpful for supporting existing ATs and it's quite handy for exposing
> > data easily with JS libraries.
> 
> Perhaps you've misunderstood what Ian is saying in your quotation.
> 
> Steve is saying that in current implementations, role="button" in that markup
> is *not* redundant since you need it to make "aria-pressed" work. If you omit
> role="button", then the button is not reported as pressed in the accessibility
> tree. Ian is saying that it *should* work even if you omit role="button", since
> ARIA allows host languages to define implicit ARIA semantics on elements and
> attributes, and HTML5 defines button as having the implied semantic of role
> button, so "aria-pressed" should apply to it the same way.
> 
> So there's a question here about how ARIA annotations do and should behave
> beyond the question of whether we should allow redundant markup.

Hi ben, yes I am saying in the limited cases where an aria-* won't work without
the addition of a redundant role, the conformance rules should not disallow the
role. In all other cases the it should be disallowed.

FYI
since this bug has been marked as wontfix I am working directly with mike smith
to work out which role/aria-* combinations need to be allowed to match
implementations, it is my understanding he will use this data to implement the
conformance rules in the W3C validator.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 13 March 2012 09:43:02 UTC