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 Saturday, 30 March 2013 03:14:14 UTC