- From: <bugzilla@jessica.w3.org>
- Date: Sat, 06 Oct 2012 02:35:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19277 --- Comment #13 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2012-10-06 02:35:21 UTC --- (In reply to comment #0) > is @hidden equal to display:none? What happens if the author changes to > display:block but leaves @hidden set? > > In discussion, the group concluded that the spec should say explicitly that > @hidden trumps all CSS. Regardless of what changes are made to CSS for an > element, all the processing requirements for @hidden elements remain in effect. > For CSS changes to have any impact, the author would have to remove @hidden. The hidden (sic!) issue here ie @hidden's mapping to ARIA-hidden="true", which causes AT to not 'see' an element such as <foo hidden style="display:block">Text</foo>. If we stopped linking hidden="" to aria-hidden="true", then the hidden issue would go away as making the hidden="" elements visible would also render them to AT. Such a change would also 'pave the way' for allowing hidden=" to be used for tab panels - see bug 19159. I don't know what the A11Y experts feel about this. If we contineu to link hidden="" to aria-hidden="true", then I agree with Tab that it could make sense to use [hidden]{display:none!important} in the user agent CSS, to make it more difficult to accidentically make hidden content visible. Such a change would also be a step towards what the A11Y telcon concluded, I think. -- 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 Saturday, 6 October 2012 02:35:24 UTC