Helping ordinary people create extraordinary websites!
| |
Helping ordinary people create extraordinary websites! |
10 Common Errors When Implementing AccessibilityBy Trenton Moss2008-01-29 
Don't use random characters to separate links
One of the more minor accessibility guidelines states that adjacent links should be separated with non-link text. The reason this guideline exists is that some very old web browsers had problems with adjacent links, whereby they ended up making all adjacent links point to the same page. This guideline is no longer relevant but can often cause accessible web developers to insert invisible characters (usually vertical bars) in between links. Unfortunately, each vertical bar is announced to screen reader users as ‘vertical bar’, which is of course nonsensical and makes it harder for these users to work through the page. Tutorial Pages: » Introduction » Don't use verbose ALT text » Don't use random characters to separate links » Don't insert text into empty form fields for the sake of it » Don't use access keys » Don't use the table summary (unless it actually adds value) » Don't forget about the content » Don't worry too much about accessibility statements » Don't agonise over acronyms and abbreviations » Don't change the tab order (unless you have a very good reason to do so) » Don't forget to listen with a screen reader
|
 |