Re: 48-Hour Consensus Call: InstateLongdesc CP Update

On Tue, Sep 25, 2012 at 12:21 PM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Silvia Pfeiffer, Tue, 25 Sep 2012 11:48:44 +1000:
>> On Tue, Sep 25, 2012 at 11:04 AM, John Foliot <john@foliot.ca> wrote:
>>> James Craig wrote:
>
>>> I'm more concerned about a link in that hidden frame, or perhaps 3 or 4
>>> links, and how/what will happen with tab-focus.  For a screen reader to be
>>> able to afford the user the ability to fire a link, it must first receive
>>> tab-focus. Yet those tab-focusable links are hidden to the sighted user.
>
>>>
> http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-mechanisms-focus-visible
>
>> you can't have it both ways:
>>
>> Either it is visible content, then it is created by Web Devs to be
>> visible and thus also accessible.
>>
>> Or it is accessibility content, then it is not visible to anything but AT.
>
> Did you mean "or it is is accessibility content, then it is not
> __accessible__ to anything but _screenreader users_" ?

Yes, screenreader users and any tools that rely on the a11y API of browsers.

> Because, like
> John said, a link inside an iframe, would be accessible for a keyboard
> user. He or she would therefore 'get lost' when the tab 'took off'
> somewhere he/she couldn't see (i.e. behind the image). (From that
> angle, it is perhaps an advantage that @longdesc does not cause the
> image to become focusable - it prevents that something steals focus.)
>
> So I don't think John's concern is "how to have it both ways". Rather,
> it is how to make sure that users only get it a single way.

My point was: what if for a particular Website the owner decides that
the long description is not relevant to be exposed visually, but would
still like to provide it to the a11y API. Thus, if we *require* it
both ways, we will end up getting nothing.

Cheers,
Silvia.

Received on Tuesday, 25 September 2012 03:10:05 UTC