- From: <bugzilla@jessica.w3.org>
- Date: Fri, 27 Sep 2013 17:54:59 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23370 --- Comment #9 from James Craig <jcraig@apple.com> --- (In reply to Leif Halvard Silli from comment #6) > (In reply to James Craig from comment #5) > > ARIA defines conflict resolution here: > > http://www.w3.org/WAI/PF/aria/complete#host_general_conflict > > > > "When a host language declares a WAI-ARIA attribute to be in direct semantic > > conflict with a native attribute for a given element, user agents MUST > > ignore the WAI-ARIA attribute and instead use the host language attribute > > with the same implicit semantic." > > WAI-ARIA should have provided examples of what this means. Bug 23383 is a less controversial example. @value, @min, and @max on <input type="range" are identical to @aria-valuenow, @aria-valuemin, and @aria-valuemax on role="slider" > For instance, I > guess that @alt on <img> is an attribute that is in direct conflict with > @aria-label. No? No. Labels are a special case. See the text alternative computation for more examples of why. http://www.w3.org/WAI/PF/aria/complete#textalternativecomputation > I feel that you are putting it on an edge, though. Even if @hidden is > boolean, it is a matter of fact that applying - or removing - @hidden on > e.g. <script>, has no effect what so ever. What? Does that mean it has no effect in browser X? In WebKit, adding @hidden hides the element from the visual display and the accessibility tree. The implementation detail is that the UA style sheet now includes: [hidden]{display:none;} > > I propose the change be to remove that line from the "strong" table (and > > possibly add it to the "weak" table) > > I concur with your proposal. Steve, do you concur too? -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 27 September 2013 17:55:00 UTC