RE: Bobby Error Message - How to fix it?

I heartily encourage everyone to look at the NEW   Bobby 3.0

1)	They have much improved and enhanced it.
2)	it is a beta   -  so if you have input or comments, or whatever   they
are most useful if you send them in as soon as possible. (it will have a
short beta cycle before being released in final form)

Oh,  the URL is

Gregg




-----Original Message-----
From:	w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Alan J. Flavell
Sent:	Tuesday, July 28, 1998 7:00 PM
To:	Al Gilman
Cc:	WAI Guidelines List; bobby@cast.org
Subject:	Re: Bobby Error Message - How to fix it?

On Tue, 28 Jul 1998, Al Gilman caused the following to appear:

    [The following text is in the "UNKNOWN-8BIT" character set]

[oh dear.  I'm going to pretend this was us-ascii]

> > One of our pages gets a Bobby error message saying that
> > "adajacent links must be separated."  Does anyone know how to
> > do this?  Someone suggested that I use a pipe | symbol between
> > the links.  If this is true, then I didn't put in the correct
> > place, because it did not work.

> This site illustrates the perils of over-reliance on Bobby results.
>
> Bobby is a great help if you know enought to take the results
> with a grain of salt.

I agree with the sentiment, albeit the wording is open to dispute.

Bobby calls attention to many overt barriers to accessibility, but has
no way of deciding (in most cases) that the author has enough
expertise to deal with these problems.  That's entirely reasonable in
my view, but it means that Bobby cannot be used as an objective
measure of accessibility, as some people seem to have assumed.

> I am copying the WAI-GL mailing list so that if I am wrong
> hopefully someone will correct me.  But I suspect that separating
> the links with line breaks is sufficient.  You shouldn't have to
> put printing characters between them -- usually " | " -- note
> the spaces around the pipe -- if there is only one link per line.

I can't argue with that, but surely it is an overkill solution?

Disclaimer: I do not make any claim to expertise about disability
access as such, but I have a bit of a track record in text-mode
accessibility issues, and there's a suggestion in the depths of my
ALT text article that I think might help here:

http://ppewww.ph.gla.ac.uk/~flavell/alt/alt-text.html

(look for the heading "Navigation to be text-friendly _and_
accessible")

With respect, I'm deleting the frightening heap of pseudo-WYSIWYG tag
salad that adorned this mail.  If only CSS has been implemented when
it was first proposed, instead of blundering down that dead alley!

Whoever it was that decided to distribute this horror to the list
certainly made a point, but I think that half a dozen lines typical of
the whole would have been more than sufficient!  It's not as if there
isn't already gigabytes of this excrement on the WWW, and more being
extruded every day by wannabeWYSIWYG authoring software, but I think
we could do without it on this list, no?

all the best

p.s pedant alert: "pipe" is a function, not a character: the character
is called "vertical bar".

Received on Sunday, 2 August 1998 14:12:12 UTC