Skip to main content
UsabilityNews.com - for all the latest in usability and human-computer interaction
BCS Interaction
 
 
The All the Latest section presents all general usability news articles


 
  advanced search
 

All the Latest

Ten common Accessibility errors


Source: Webcredible, 5 April 2008
Submitted by Trenton Moss

Web developers attempting to build accessible websites often make the same mistakes time and time again. Although they're trying their hardest, sometimes their overzealousness gets in the way and actually hinders the accessibility of their websites.

The 10 guidelines below tell you what not to do, so you too don't fall foul of these same common accessibility errors...


1. Don't use verbose ALT text
Accessible web developers often insert far too much ALT text on to images, in the hope that this will help screen reader users. ALT text for information-based images should be short and succinct, and contain no more information than is in the image. Decorative images should always be given null ALT text, or alt="", so that they're ignored by screen readers.

2. Don't use random characters to separate links
One of the minor accessibility guidelines states that adjacent links should be separated with non-link text, because some very old web browsers had problems with adjacent links. This guideline is no longer relevant and any invisible characters (usually vertical bars) are 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.

3. Don't insert text into empty form fields for the sake of it
Another old and outdated guideline states that any empty form field should have placeholding text inside of it. This guideline originally existed as very old screen readers weren't always able to pick up empty form fields. All major screen readers now pick up empty form fields so it's safe to ignore this guideline.

4. Don't use access keys
You can assign access keys to any link to provide keyboard shortcuts to them. In reality, access keys can override keyboard shortcuts for screen readers, rendering key screen reader functionality useless. The other problem with access keys is there's no convention, so the few sites that use them do so in whichever way they choose.

5. Don't use the table summary (unless it actually adds value)
Screen readers read table summaries aloud, providing a summary of the table content prior to listening to the whole table. The table summary should always be omitted from a layout table. Websites using a tabular layout sometimes have table summaries of ‘layout table’ which of course add no value at all.

6. Don't forget about the content
The way that content is structured on any website is an enormous part of accessibility. A website may be perfectly coded and conform to the highest coding standards, but if its content is poorly structured, the site will prove difficult to impossible for some special needs web users. Consider front-loading content so that each paragraph begins with the conclusion, and ensure content has been broken down into manageable chunks with descriptive sub-headings. Use lists wherever appropriate, and stick to plain and simple language.

7. Don't worry too much about accessibility statements
Many websites attempting to offer great accessibility create lengthy accessibility statements, typically containing information on the accessibility features of the website. Disabled or not, as web users we don't tend to consult 'help' guides on any site - rather, we stumble along attempting to complete our goals. Although there's nothing wrong with making an accessibility statement page there's no need to spend too much time on it.

8. Don't agonise over acronyms and abbreviations
Declaring whether something is an acronym or abbreviation is easy to do in the HTML, simply by using the or tags. The full acronym or abbreviation can then be expanded upon within this tag. Most screen readers don't support these tags though so they don't really offer much of a benefit to disabled users.

9. Don't change the tab order (unless you have a very good reason to do so)
The tabindex attribute can be used to change the on-page tabbing order but is rarely necessary. Screen reader and keyboard-only users tab through links and form items in the order in which they're placed in the HTML source code. Provided that users tab within each section roughly from top-left to bottom-right (which they will) then the tab order is perfectly adequate.

10. Don't forget to listen with a screen reader
Whilst you're building your accessible website don't forget to keep testing the pages as you build them. In particular, you'll want to listen to them with a screen reader to check that accessibility features work as planned.

 


External link to another web site Associated Link:
Webcredible - user experience consultancy


Other News

Poor Shopping Basket Usability will hinder Christmas Rush
Source: UN, 20 November 2008
 
A new study from eDigitalResearch identifies customer service and online shopping basket usability as the two key areas where online retailers need to improve.

Future Phones to Read Your Voice, Gestures
Source: Wired, 19 November 2008
 
Five years from now, it is likely that the mobile phone you will be holding will be a smooth, sleek brick — a piece of metal and plastic with a few grooves in it and little more.

Why Digital Research is important in tough Financial Times
Source: Financial Times, 18 November 2008
 
With the banking sector moving towards consolidation, it is crucial that customers are understood, reacted to and rewarded for their loyalty.

Get Ready for 'Ergobamanomics'
Source: AssemblyBlog via ergonomics in the news , 17 November 2008
 
Is President Elect, Barack Obama, a secret ergonomics and usability enthusiast?

The Most Dreaded Keyword Phrase
Source: SearchEngineLand, 15 November 2008
 
In website usability, one of the hardest obstacles to overcome is the mentality of “This is what I would do.”

User Experience Standards Missing from Web 2.0 Designs
Source: UN, 14 November 2008
 
Usability professionals should be more involved with the development of Web 2.0 tools.

New technology showcased at World Usability Day
Source: User Vision, 13 November 2008
 
Today is World Usability Day!

Review: 16 User Interface Prototyping Tools
Source: Dexo Design, 12 November 2008
 
People constantly ask me what the best prototyping or mockup tool is, so I decided to do a review of all the tools I’m aware of.

Radio 4's PM show announces Winner of 'Show Us a Better Way'
Source: BBC, 11 November 2008
 
Ever been frustrated that you can't find out something that ought to be easy to find? Ever been baffled by league tables or 'performance indicators'?

Cisco Systems extends Product Usability Research
Source: Catalyst Resources, 10 November 2008
 
Cisco is conducting extensive usability research with Catalyst Resources, into complex new technologies.

 
 

 

home | contribute | subscribe | news feed/RSS | search | contact us | disclaimer

UsabilityNews.com (version 1.41), along with its associated web site and content,
are all strictly © Copyright of the BCS Interaction 2001-2008. All rights reserved.

Joanna Bawa (editor), Dave Clarke (founder, designer and developer). Ian Parry (graphics).