TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
--- David Berg <dberg -at- dmpnet -dot- com> wrote:
> Do you know how software readers handle the Title tag? Also, I
> presume that software readers must make use of the alt text in some
> fashion...do you know what it takes for a blind user to follow a link
> that they discover via the alt text that didn't appear in the links
David, I don't know nearly enough about how software readers handle
either tag. I have worked with the Amaya browser, for it's text-only
capability, which has given me some small insight. I've also found one
text-reader, but it seems to convert the visible content of a web page
into spoken text and makes no provisions for hyperlinks, graphics, alt
text, or title text.
>From what I've seen--and I'm sure I'll be corrected on the list
<g>--the quality of software available for the visually impaired is, to
use a purely technical term, sucky.
What I've been doing, and what I would recommend to everyone, is
following the W3C's Web Accessibility Initiative, http://www.w3.org/TR/WAI-WEBCONTENT/. They have an excellent set of
guidelines that can be followed as a standard both for developing
content and for assessing its accessibility. It is from these
guidelines that I came to understand that "click here" was a 'bad
thing'. I quote: "Use text that makes sense when read out of context.
For example, avoid 'click here.'"
The W3C WAI site also provides checklists and levels of accessibility
to which a developer can aspire. I think it's well worth the read for
those concerned about web accessibility. Those who aren't concerned
about it ought to be. Like every other aspect of doing a good
communications job, it's easier to do it right the first time than it
is to do it wrong over and over again.
Oh, an added benefit for most content developers is if you follow the
WAI Guidelines you have fewer problems with browser compatibility
issues than if you work to one browser and try to fix your code for all
others. Or so my experience leads me to believe.
> I worked for quite awhile on a medical web site doing a complete
> rewrite and reorganization. Many of the users that access this site
> have spinal injuries, so I tried to keep the navigation simple as
> possible, and provided alt text for the few graphics I used. One
> resource folks might keep in mind when designing web sites is Bobby,
> a web site that helps identify barriers to access by disabled users.
> You can find it at : http://www.cast.org/bobby/
Thanks for the added resource. I'll be checking it out.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.