W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2011

Re: Response to: ChangeProposals/DeprecateLongdesc

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 24 Aug 2011 11:00:11 +1000
Message-ID: <CAHp8n2n3VLgdQ+-mXu9uBO-tYzWNkvz0th6QsM36WLovNN4P+Q@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, John Foliot <jfoliot@stanford.edu>, public-html-a11y@w3.org
On Wed, Aug 24, 2011 at 9:00 AM, Janina Sajka <janina@rednote.net> wrote:
> Silvia Pfeiffer writes:
>> Note that your proposal strongly supports the move of @longdesc to the
>> context menu, which in turn makes the availability of a @longdesc link
>> much harder to discover for screen reader users because they have to
>> open the context menu to find out, while @aria-describedby will just
>> push the description at them. So, if anything, the discoverability
>> argument is not going in your favor.
> This is not correct. It is expected AT will provide suitable mechanisms
> to identify the availability of long desc, as indeed AT is able so to do
> today as shown in the TF backed proposal:
> http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc/Implementation
> The actual point of providing longdesc via a mechanism like the context
> menu is to allow any user, not just AT users, to access this content.
> This was an oft repeated criticism in earlier discussions. While not an
> a11y requirement,it's certainly a usage the TF does not oppose. If the
> WG wants longdesc to be sharable across all users, more power to the WG,
> the TF has never objected to that.

OK, can we make sure that the proposal explains that longdesc's
availability should both be announced by screen readers upon reaching
the image and be in the context menu? This wasn't clear to me from
reading the document.

Received on Wednesday, 24 August 2011 01:00:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:23 UTC