W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Jan 2011 10:16:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PdKE9-0003LZ-Kf@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11557

--- Comment #15 from steve faulkner <faulkner.steve@gmail.com> 2011-01-13 10:16:20 UTC ---
(In reply to comment #14)
> Comment 11 suggests that it's acceptable for a site with only a few AT users to
> not be accessible to those AT users, which seems counter to what I normally
> hear from the accessibility community.
> 
> On balance it seems that the issue raised in comment 10 is largely academic and
> completely outweighed by the issue raised in comment 0, comment 1, and comment
> 3, and no other use cases have been raised (despite comment 4 saying there are
> "many legitimate use cases"). However, I could see an argument being made for
> the position in comment 10. I don't see any argument for the status quo.
> 
> Could someone from the a11ytf clarify the tf's position on comment 10?


> despite comment 4 saying there are "many legitimate use cases"

as implemented in any case where an author wishes make use of a state or
property that is particular to a role
example: aria-pressed on the button role the role needs to be explicitly added.

<input type=button role='button" aria-pressed=true>

-- 
Configure bugmail: http://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 Thursday, 13 January 2011 10:16:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 10:16:28 GMT