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

Re: why are we pursuing this idea? (was: Implementation Details request on Issue 204 Decision)

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Tue, 21 Aug 2012 23:59:59 +0100
Message-ID: <CAEhSh3dVhz14o6R2X4KA1MnJFaNJOok_=RgE_GazrE5p8LkV+A@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, Chaals McCathieNevile <w3b@chaals.com>, John Foliot <john@foliot.ca>, Maciej Stachowiak <mjs@apple.com>, public-html@w3.org, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Tue, Aug 21, 2012 at 11:50 PM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> * He also says that 'If we do implement this, it will only be as a
> temporary solution because of the lack of support in current accessible
> browsers'. This is a technical argument. But it sounds like a incorrect
> technical argument. At least today - 2 years later - where we hear that
> Firefox *does* support @longdesc, in the accessibility API - which I
> assume that NVDA would use.

I think by support James means "discoverable to *all* users, not just
users of assistive technology". So just having a hook in the
accessibility API doesn't count.

Interestingly, James notes that users can access some @longdesc instances:

"you can already access longdesc for non-linked, non-clickable images
with NVDA in Firefox if you press enter on the image. The presence of
longdesc is not reported, however."

My guess is this is because opening the longdesc is exposed by Firefox
as an action, and the enter just triggers whatever primary action is
associated with the accessibility node in focus.

Benjamin Hawkes-Lewis
Received on Tuesday, 21 August 2012 23:00:52 UTC

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