WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: non-link characters (was header tag)

for

From: Alastair Campbell
Date: May 1, 2003 3:49PM

Hi Julian,

That's a useful technique - I use exactly the same one! However, I think it is less necessary for the visually impaired than people using visual browsers.

It is possible to make it very difficult for most people to discern the gap, e.g.:

<p>This paragraph <a href="#1">contains </a><a href="#2">two</a> anchor tags</p>

There would be no visible gap, however, a screen reader would know that there are two links and read out something like:

"The paragraph LINK contains LINK two anchor tags." (I'm sure this isn't exactly right, but I think it's close.)

My question is: Are there any other (currently used) user agents where a lack of non-link characters between links is a problem?

Having lots of links together might make things somewhat unclear in a text browser like Lynx, but it isn't difficult to work out as you move through the links because they change colour one at a time.

Are there any current situations where it would be a problem? (Or is it a guideline that needs depreciating?)

-Alastair

On May 01 15:00, <EMAIL REMOVED> wrote:
> the vision
> impaired who can't detect the break in the underline, they cannot "see"
> where one link ends and the next begins. I have used an "invisible pipe
> character" to separate links before such as Link1 | Link2 | Link 3. The pipe
> characters "|" are hidden using <span class="invisible">|</span> where the
> invisible class is defined as display:none.


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