articles
Accessibility issues for web designers
Definition: Accessibility
For a website to be accessible, people with or without disabilities must be able to perceive, understand, navigate and interact with websites.
Why should web site owners be concerned?
In the UK it is actually illegal for a service provider to discriminate against disabled people. So, this means that websites providing a service need to cater for all users, abled or disabled, sighted or non-sighted. How do you make a website accessible to a blind person? Technology provides the answer through the use of screenreaders - these pieces of software do their best to read out information displayed on a website. As a web site owner, there are key measures you can take to ensure that a web page is as friendly as possible to screen readers (one example would be using text instead of images).
Around 2 million people in the UK self-define themselves as having a sight problem or seeing difficulty. Source: http://www.rnib.org.uk
Benefits of accessibility
As it turns out, making a website accessible can really enhance your search engine rankings - essentially because you're making the content of your site much more visible to search engines. Layout and images are generally removed to external stylesheets which the search engine spiders can ignore.
How do I check if my website is accessible?
There are a number of guidelines set out by the W3C (World Wide Web Consortium) relating to accessibility. These break down as follows:
- Priority 1
A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.Example
Checkpoint 1.1: Provide a text equivalent for every non-text element (eg via "alt", "longdesc" or in element content)... - Priority 2
A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.Example
Checkpoint 2.2: Ensure that foreground and background colour combinations provide sufficient contrast when viewed by someone having colour deficits or when viewed on a black and white screen. - Priority 3
A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.Example
Checkpoint 4.2: Specify the expansion of each abbreviation or acronym in a document where it first occurs.
- A: All priority 1 checkpoints are satisfied
- AA: All priority 1 and priority 2 checkpoints are satisfied
- AAA: All priority 1, priority 2 and priority 3 checkpoints are satisfied.
There are a number of automated website checkers out there where you can simply enter your website address, and you'll be informed of any 'errors' relating to accessibility. Whilst useful, these should not be relied upon. For example, an automated checker will tell you if an image has alternative text, but it cannot tell you if that alternative text is sensible and related to the image in a meaningful way.
Useful links
Organisations
Date posted: 20 Jul 2007