- From: Al Gilman <asgilman@iamdigex.net>
- Date: Thu, 21 Feb 2002 19:00:08 -0500
- To: goliver@accease.com, jm.damour@camo.qc.ca
- Cc: w3c-wai-ig@w3.org
At 04:05 PM 2002-02-21 , goliver@accease.com wrote: >However, perhaps a better solution would need to be >found? > I think we should. Compare with <http://lists.w3.org/Archives/Public/wai-tech-comments/2001May/thread.html #0>http://lists.w3.org/Archives/Public/wai-tech-comments/2001May/thread.html#0 (whole thread) Al >Hi Jean-Marie >I confirmed this behaviour when the *image is a link*. > >This has interesting consequences for the sort of >design where there are two links side by side to the >same place (an image link and a text link),to aid >people who may prefer image navigation. > >I think the IBM site (as an example) chose to have >alt="" for the image in order not to have the same link >text read out twice in a row. >However, perhaps a better solution would need to be >found? > >I don't like using alt = " " on an image as a link >because when you mouseover you get a little box, which >can be confusing! > >For clarification when the image is *not* a link alt="" >does *not* read the name of the image. > >Cheers >Graham > >On Mon, 18 February 2002, jm.damour@camo.qc.ca wrote > >> >> >> Hello all, >> >> In JAWS 4.01, for an image with a null alt text >(alt=""), JAWS read the name >> of the image. If alt is alt=" ", JAWS don't read the >name. >> >> I think it is a result wich can surprise many Web >designers. >> >> Jean-Marie D'Amour, M.Ed. >> CAMO pour personnes handicapées >> <http://www.camo.qc.ca/>www.camo.qc.ca >> Montréal, Québec, Canada > >AccEase Ltd : Making on-line information accessible >Phone : +64 9 846 6995 >Email : goliver@accease.com >
Received on Thursday, 21 February 2002 19:00:02 UTC