WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 10.5 Separate adjacent links

for

From: Glenda
Date: Mar 22, 2005 1:15PM

Thank you, Terence!

That is the explanation I was actually looking for -- in case the client
asks why the site isn't Bobby-approved [even though it complies with Web
Content Accessibility Guidelines 1.0, as far I know]. Some clients put so
much credence into Bobby and other automated checkers, without fully
understanding what makes a site accessible.

Cheers,
Glenda
Soaring Eagle Communications
www.eaglecom.bc.ca

-----Original Message-----
From: terence [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, March 22, 2005 11:08 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] 10.5 Separate adjacent links



<EMAIL REMOVED> wrote:

I used a white vertical bar to separate the adjacent links in the top
navigation bar. Is this not adequate? Bobby is spitting it out, saying
repairs are needed. Is this another example of how automated checkers
should not be relied upon as the gospel?....

My experience with Bobby 5.0 has been if there are additional HTML
elements between the links surrounding a printable character, Bobby
thinks the character is not there. I got errors on a site I worked on
where I had inserted a span element around a vertical bar, with CSS
instructions to match the background color. Bobby reported an error;
when I removed the span elements, it passed. I sent samples to
Watchfire with an explanation of what was happening shortly after Bobby
5.0 came out. Bobby 4.01 (the Java version), slightly revised by
Watchfire, did all right with this scenario. I haven't tried the on line
version with this.

Terence de Giere
<EMAIL REMOVED>

----
To subscribe or unsubscribe, visit http://www.webaim.org/discussion/

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.0 - Release Date: 3/21/05

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.0 - Release Date: 3/21/05