- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Dec 2012 12:31:24 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20420 --- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> --- (In reply to comment #5) > Hi leif, will leave this open for now, but in regards to use o > role=presentation on any elements see: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=11956 Regarding bug 11956, then that was marked (by yourself!) as a duplicate of bug 10919. Anyway, this is what I get out of bug 11956: The example you gave in bug 11956 was <input type=submit role=presentation >. Which per HTML5 belongs to the strong table. Your claim about that example was that HTML5 back then allowed role=presentation. You did not cite any spec text for that claim, however, so I wonder if it was based on memory rather than spec text. (Or if Ian resolved it after he updated the spec to not allow "presentation" for strong native semantics elements.) As for the parallell "mother bug", bug 10919, then Ian’s resolution was that "Per comment 17, for focusable elements such as those listed in comment 14 we are better off relying on ARIA to apply the relevant conformance criteria here." So it does seem as if Ian considered that HTML5 should not define whether it, for your example (<input type=submit role=presentation >) from bug 11956, would be conforming to use presentation role, but rather leave that question to ARIA. And that is what HTMl5 currently does. According to Ian’s ruling, this conclusion required not spec change, and may be it is the "no spec change" bit which is the confusion point? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 19 December 2012 12:31:26 UTC