On Apr 5, 2013, at 4:51 PM, Mark Sadecki <msadecki@w3.org> wrote: > On 4/5/13 6:41 PM, James Craig wrote: >> Feedback on aria-hidden section of "Using WAI-ARIA in HTML" document >> https://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html >> >> @hidden versus @aria-hidden section of the attributes table: >> >> Element with a hidden attribute aria-hidden=true NO Use the hidden attribute in conjunction with the CSS display:none property >> >> >> There are differences between the two which should be called out. @hidden always hides content from all modalities, so this will result in the visible removable of the content in addition to removing that content from accessibility contexts. >> >> Depending on the UI design of a web interface, there are times when content needs to be hidden from screen readers. For example, sometimes content is rendered partially at the edge of a view (like a carousel) to indicate there is more that will become active once you click Next or scroll. In these circumstances, using @hidden would prevent the visual rendering of this "lead-in" content, so the document should recommend using @aria-hidden at some times. > > Thanks for your feedback. I think we are in agreement that there are use cases which would benefit from explicitly defining a value for "aria-hidden". However, this matrix is referring specifically to an element with a "hidden" attribute. In this context, there is no reason to explicitly state aria-hidden=true as it is the default state for any element with a "hidden" attribute, unless I'm misunderstanding your use case. Thanks Mark, I see now that you're right it's not needed in this case where @hidden is explicitly stated. An example where @aria-hidden="true" would be needed on "rendered" content is in addition to the @inert attribute. http://www.w3.org/html/wg/drafts/html/master/editing.html#the-inert-attribute
Received on Monday, 8 April 2013 18:43:26 UTC