Do it yourself accessibility
Website accessibility is not something that can be fully checked or validated by some or other automated process . At most these tools can check our pages against some of the accessibility checkpoints. Most of the checking still has to be done manually.

photo credit: Arnþór Snær
I often get asked just what these manual checks should include.
This is not an easy question to answer unless I tell you that you have to check your pages against each and every accessibility standard. Many people do not understand the technical jargon used in the standards themselves and most do not have the time to follow this advice.
Let me try and ease this situation by telling you what I would check on my web pages:
Cross-browser capabilities
Simply open your pages in Internet Explorer, Firefox and Opera if you can (any two of these would suffice). Check that your pages actually appear and act the way you expect them to in all the different browsers you have available.
Links clearly described
If the wording in the actual link is not clear enough you need to make use of the title attribute to describe each link. Links like ‘click here’ should be avoided at all times, they are meaningless.
Working Links
Do all your links actually work? Does clicking them take you to the page you expect them to?
New windows
If you have to use ‘new windows’ do you warn your users about this fact?
Keyboard navigation
Can your pages be navigated without using a mouse. If you cannot do this neither can any keyboard or voice-only user.
Text re-sizing
I am not speaking about changing the screen resolution or using some or other maginifying software. Can the text on your pages be re-sized within the browser itself? All browsers have implemented this functionality differently so you will have to play around to find out how your favourite browser has implemented it.
Forms accessibility
Checking forms is a simple task. Simply click on any label on your form. If your form has been coded correctly this will put the focus inside the relevant control next to the label you have clicked. To do this you need to make use of the label element.
Audio content
If you have some kind of audio content on your pages let’s pretend that you are deaf for a minute. Turn off your speakers. Does this content make sense to you now? You need to provide alternative transcripts for all your audio content.
Another one to remember here is that you must check to see that you are not forcing any audio content onto the user by playing the audio automatically. A user should have the option of turning the audio on and/or off.
Alternatives to graphics
Here we need to remember that not all browsers support images. Some users also prefer to browse without images even though their browser may support them.
The trick to images is the use of the Alt attribute. Whatever you set in these is what a user will see (or hear) if images are turned off for whatever reason.
You have to differentiate between images that actually convey some form of content and images that are used purely for decorative purposes. If the image is part of the content you need to tell the user via the Alt attribute what the image is all about. If the image is there purely to make your pages look pretty you need to use an empty Alt attribute (alt=”"). Browsers that do not support images will ignore images that have an empty Alt attribute set and the user will never even know the image was there. Never leave the Alt attribute out completely.
Check spelling
Now what has this got to do with accessibility? If your spelling on your pages is incorrect the so-called speaking browsers will pronounce the words incorrectly.
Blind users
A quick and free way of interacting with your site the way a blind user would is to view your pages through the Lynx Viewer.
Site map
If users get lost on your site you have done something wrong. A good old fashioned site map normally takes care of this. Has your site got one?
Contact details
If you are truly interested in your users you will ensure that your site has an easy way for a user to contact you should they experience any difficulties in using your site.
This is by no means an exhaustive list but it should be sufficient to get you going along the road to full website accessibility.
There are many people out there that would love to visit and use your site. Give them a chance, make your site as accessible to as many as what you possibly can.
These posts might be related:








Hi, my name is Lyndi. Here we talk about all things related to WordPress. You are more than welcome to join in the discussion.


There are currently 107 posts with 952 comments on this blog.
I still have a problem figuring out sitemaps to facilitate search engine searches. I know that there are websites that will give one the XML code and so on - I’ve done that - but what does one DO with it? I use Blogspot - how does one add a seperate sitemap page?
Mike, there are actually two types of ’sitemaps’. The one is a xml file (this is the one you referred to) which you upload to Google’s Webmaster Tools. This helps Google to index your pages more efficiently (or so they claim anyway). This I do through a plugin in WordPress.
The other is a normal sitemap page like the one on this site (this is what I was referring to in this article). This is simply a list of all the pages and posts on the blog which is automatically updated everytime I post something new. This I also did via a plugin. How you do this in Blogspot I have no idea. I suggest you do some Googling.
Thanks, Sailor, will do.
Great simple article.
Re the browsers I would really be recommending to try them all. You shouldn’t have to but IMHO experience shows you do.
The alt text on images is also a requirement for most recent web standards (thereby dual benefiting) as we have said in the past.
You can also install Lynx itself rather than a viewer (I have found that the viewer can be a little bit Wookie sometimes when compared to the Mac/Win/Linux executables.
@Mike, what server side technology do you use? (PHP/ASP/PERL etc) there are a number of scripts which can convert your sitemap.xml into a viewable and useable visual sitemap for your site.
Keep up the good work