W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

RE: longdesc requirements Re: alt tags for graphs

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Mon, 1 Apr 2013 09:09:15 -0400
Message-ID: <67893fa4b4002ce96bc0f558bd3d36e4@mail.gmail.com>
To: Sailesh Panchang <sailesh.panchang@deque.com>, Charles McCathie Nevile <chaals@yandex-team.ru>
Cc: "Frank M. Palinkas" <fmpalinkas@gmail.com>, David Woolley <forums@david-woolley.me.uk>, "Mattingly, F Darrell" <darrell.mattingly@uky.edu>, WAI Interest Group <w3c-wai-ig@w3.org>, "Guettler, Karen M" <kmguet2@uky.edu>
[Sailesh wrote] So I believe this implies users who do not employ  heavy
duty AT (screen readers/magnifiers and such) are expected to install
plugins / extensions for access to skip nav links, longdesc content, etc.
What do you think?

What plug-in can I install into Safari on my iPhone to access longdesc or
alt?

People can say all day -- browsers should support these items or just
install a plugin, but let's be realistic.
1. Most browsers never implemented access to skip to main content,
longdesc, etc.
2. IE was forced to remove access to alt on images via tooltips to be
standards compliant
3. Many browser such as those on mobile device don't adequately support
plug-ins
4. Installation of plug-ins slows down browsing and/or user agent loading
5 Installation of plug-ins requires locating and even knowing these exist.


Jonathan

-----Original Message-----
From: Sailesh Panchang [mailto:sailesh.panchang@deque.com]
Sent: Friday, March 29, 2013 11:14 PM
To: Charles McCathie Nevile
Cc: Frank M. Palinkas; David Woolley; Jonathan Avila; Mattingly, F
Darrell; WAI Interest Group; Guettler, Karen M
Subject: Re: longdesc requirements Re: alt tags for graphs

>> I have no problem with programmatically associating long description
>> or long description links with an image but it MUST be available to
>> all user groups without having to install special plug-ins or run
>> assistive technology to access or make user agents display
>> information that others can access without such requirements.
>
> I agree that user agents that don't make longdesc available to all
> users all the time are not doing as well as they should. Putting
> requirements in
>
> specifications doesn't, by itself, change implementations. But I
> welcome input on strengthening the requirements...

Sailesh:
Is this unrealistic ... especially the part about not requiring AT?
Some folks require AT for computer access. Period.
And AT is able to interpret Web page content   etc.
But even users who ordinarily do not employ AT might be required to employ
special purpose plugins / extensions as WCAG-WG opines with respect to
sufficiency of H69 for skipping repetitive content blocks (SC 2.4.1):
http://lists.w3.org/Archives/Public/public-comments-wcag20/2012Sep/0009.
<startQuote>NOTE:  All of our techniques assume that people needing
special user agents (including AT or special plug-ins) will get and be
using that type user agent (eg screen reader, or plug-in that allows
keyboard navigation of properly marked up content, etc)<endQuote>

So I believe this implies users who do not employ  heavy duty AT (screen
readers/magnifiers and such) are expected to instal plugins / extensions
for access to skip nav links, longdesc content, etc.
What do you think?
Sailesh Panchang
www.deque.com
>
Received on Monday, 1 April 2013 13:09:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC