W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2010

Re: ISSUE 30 @longdesc use cases

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 23 Aug 2010 15:18:37 -0700
Message-ID: <AANLkTikYKMpAPH5qQM=Bt6bWVYmvUNuQ9z+mEK_9RXX4@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Joshue O Connor <joshue.oconnor@cfit.ie>, HTML Accessibility Task Force <public-html-a11y@w3.org>, HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>, Barry McMullin <barry.mcmullin@dcu.ie>, Laura Carlson <laura.lee.carlson@gmail.com>
On Mon, Aug 23, 2010 at 2:42 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Mon, 23 Aug 2010, Jonas Sicking wrote:
>>
>> Note that the 'hidden' attribute prevents the description from being
>> displayed inline, but doesn't prevent it from being exposed to AT users.
>
> It should... The hidden="" attribute means "this is irrelevant and must
> not be presented to the user".

Define "presented to user".

A <style> element inside a @hidden element still affects the
presentation of the whole page. SVG patterns, markers and <use>
elements that point to elements inside a @hidden element is still
rendered right? Form controls are still submitted, and javascript is
still run, the effects of this is often visible to the user.

/ Jonas
Received on Monday, 23 August 2010 22:19:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:09 GMT