accessibility

adjacent links

[HelenDev]

Trying to make my site accessible...

[w3.org...]

I didn't know about this before, but am I correct in thinking that links laid out like this

link1 ¦ link2 ¦ link3

will suffice on this point?

[encyclo]

Short answer: yes. Longer answer: you might want to check in a screenreader what happens when you use the ¦ character just in case. I can't check it right now, but I think it's safe.

[Matt Probert]

Screenreaders are all different, but generally handle any normal characters. Try using Lynx if you want to check accessibility and also search-engine friendliness of a page.

Matt

[datadame]

I use pipes to separate text links and have had no problems that I've found or that have been reported by users.

Since you're offering text navigation, you might want to also add (if you haven't already done it) a text link near the top/beginning of the page that directs the user to the collection of text links you're building, if that collection isn't going to be near the top of the page. Something like "click here for text navigation" near the top/beginning of the page can save screen-reader users from having to listen to the entire page being read to them while they wait to find out whether or not they can easily navigate.

[vinzzz]

tip:
put hyperlinks that shoudl appear next to eachother in a list. Nothing better than a list. Screenreaders/textreaders read them perfectly and its clean markup aswell

[HelenDev]

Thanks for the replies guys :)

On a similar topic, I'm now at the stage where I'm Bobby testing my page. I have a couple of errors where it says

"Separate adjacent links with more than whitespace."

Well, I have done this for my text as discussed, but this refers to a couple of images which have links. One is seperated from the next one with two line breaks (which you would think would be enough?) but admittedly the other instance has two images seperated by  

What's the solution here? I don't really want to put invisible images or text in because I feel it's missing the point of the whole accessibility/proper markup debate. Or is there something simpler I haven't thought of? Any suggestions very welcome :)

[vinzzz]

just read my comment again :D
ALL things that react as a list SHOULD BE in a list. Its the perfect seperator if your images work as list-items, such as a menu

[tedster]

You might use CSS rules like this to get a horizontal list of links:

ul {list-style-type:none;}
li {display:inline;padding-right:6px;}

[dannyb]

Using a list (<ul><li> etc.) can give a clean clear semantically correct navigation bar, and can be styled with CSS to work in any format you want - vertical or horizontal.

There are a number of good articles on 'A List Apart', and online standards and accessability magazine. 'CSS Design: Taming Lists' is a good article.

[HelenDev]

Cheers for your help guys :)