Citizens With Disabilities - Ontario
"TOGETHER WE ARE STRONGER"

         



The Power Of Five

The local government Society of IT Management (Socitm)(http://www.socitm.gov.uk/socitm/) this week published a report on website accessibility which included a round-up of the five most common accessibility errors.

The society estimates that these five errors account for 76% of all website accessibility failures, and it asked Robin Christopherson, Head of Accessibility Services at the charity AbilityNet (http://www.abilitynet.org.uk/), to describe their impact. Robin is blind and uses the popular 'JAWS' screen reader software to access the web.

An edited version of Robin's assessment follows.

"Common Failure 1 Is To Have No Alternative Text For Images.

"This is an extremely common occurrence. I visit a website and am confronted with numerous unlabelled images. For mouse users this 'alternative text' is what pops up when you hover over the image. The average web page has dozens of images, from photos and adverts to 'eye-candy' such as spacing graphics and design flourishes. Many of these images are also clickable links or buttons, and not knowing what these are makes navigation impossible. Imagine trying to drive from A to B where the signposts at every roundabout or junction are blank. A disaster!

"Every single image on a website should be properly labelled. You don't need to begin captions by saying "Picture of.", as I already know it's a picture. You don't need to label 'spacer' or 'eye-candy' images (but give these a default caption so that the page still passes the accessibility checkers) and, above all, make sure that all images that are also links or buttons describe what will happen when you click on them, e.g., alternative text as "Marilyn Monroe - click to read her life story".

"As well as revolutionising the site for blind users, labelled images will also help those with dyslexia and literacy difficulties who use text to speech software (they hover their mouse over any text or image and the content is spoken out). It will also help those with images turned off (many hand-held users do not display images) and, last but by no means least, Google loves labelled images.

"Common Failure Two Is The Inappropriate Use Of JavaScript.

"JavaScript is used to write mini-programs that are embedded in web pages and can enhance their functionality. They are very widely used and set to increase dramatically with 'Web 2.0' applications.

"My screen reader (JAWS) is one of the most sophisticated, but there are still many occasions when some uses of JavaScript leave me confused or frustrated, roaming at length to discover what bit of the page (if any) has changed after clicking that link, or finding that I am totally unable to access that shopping cart as selecting that button using the keyboard does nothing at all.

"It isn't enough to offer an alternative for those not using JavaScript, thinking that disabled users do not have JavaScript switched on as a matter of course. The vast majority of users of assistive technologies (such as screen readers, voice recognition, magnification, alternative keyboards and mice) can benefit from JavaScript functions as much as anyone, with the major caveat that there are certain uses of JavaScript that are not accessible to these technologies.

"The simple solution is to test your pages with these technologies to ensure that your particular application of JavaScript is not problematic.

"Common Failures 3 And 4 Are Errors In Simple And Complex Data Tables.

"Thankfully, these days most websites use style sheets rather than tables to style and arrange the blocks of content on a web page. Where data tables are concerned, however, it is still the case that most are not coded in such a way that the relevant headings are spoken by a screen reader when moving from cell to cell. I hear '1327' and '1727' with no idea of whether these are sales of widgets or notable dates in history.

"The solution is to make sure that all headings of columns and rows are coded using the 'th' tag instead of the 'td' tag. A screen reader will then announce these along with the contents of the cell, putting the data in context (eg "Widgets sold in June, 1327").

"And Finally, Common Failure 5 Is The Use Of Features With A lack Of Accessible Alternatives.

"Here you are confronted with an inaccessible bit of content or function and you search for a way around the obstacle, but to no avail. A classic example is 'CAPTCHA'. A CAPTCHA is a type of security test used to determine whether the user is human (and so exclude automated spamming programmes). A common type of CAPTCHA requires that the user type the letters of a distorted image. Since the image is by definition unlabelled (as otherwise it can be read by malicious software) an alternative (such as an option to register by phone or email) is essential.

"When it becomes clear that you have content or function that cannot be made accessible, offer an accessible alternative. For example, the Google accounts sign-up process that uses CAPTCHA also has a link to an audio version of the code to be entered plus a link to contact customer services for those who cannot access either the visual or the auditory option.

"Always remember that an accessible site is a popular site - and not just for the disabled community. Research has shown that a site that is designed with accessibility in mind is also easier to use by all."

The Blind Speak

I found this in Dan Jellinek's E-Access Newsletter for April 2008 (http://www.headstar.com/eab/). It describes the five most common web accessibility problems from the perspective of a blind user. Very informative.

BTW, I have been publishing a series of articles regarding accessibility (http://mainecite.org/awd/accdocs.html) on the Maine CITE Accessible Web Design site (http://www.mainecite.org/awd/) and just so happened to do one recently on this same topic. Check that out too since I provide resources for how to find and fix the issues mentioned here.

Reproduced from http://jebswebs.net/blog/index.php?itemid=40

More accessibility articles.