IT-Analysis.com
IT-Analysis.com Logo
Enterprise SME Business Issues Technology Services Channels
Module Header
David TebbuttTeblog
David Tebbutt
19th November - Collaboration: the old way. Why not?
Martin BanksBanks Statement
Martin Banks
18th November - This Cloud has a silver lining
Peter AbrahamsAbrahams Accessibility
Peter Abrahams
18th November - Major new accessibility features in Firefox 3.0.4
Martin BanksBanks Statement
Martin Banks
17th November - Psychology of data ownership may be changing at last
Tony LockFreeform Comment
Tony Lock
16th November - Clouds yet to fill the IT skies
Module Header
Q. Which database do you use most?
 
  • addtomyyahoo4
  • Subscribe in NewsGator Online
  • Add to My AOL
  • Subscribe with Bloglines
  • Add to netvibes
  • Add to Google
Blogs > Abrahams Accessibility
Accessible to whom?
Peter Abrahams By: Peter Abrahams, Practice Leader - Accessibility and Usability, Bloor Research
Published: 23rd October 2007
Copyright Bloor Research © 2007
Logo for Bloor Research

In my last blog I discussed the case against Target. It generated a lively discussion with a number of readers. One of these comments was so serious that I decided I should start a new thread. The comment was “It sounds ugly to say, but how disabled does a person have to be before designing a website to accommodate them is considered unreasonable and a web designer is not legally responsible to accommodate them? Blind? Deaf? Limbless? What if they are mentally retarded?”.

Blind

The question should really be 'vision impaired' and the website should be able to support users with vision impairments. But for this blog I will stick to people who are registered blind and use a screen reader to help them interact with the website.

The person cannot see images or video and there is no way that either can be fully described, however it is perfectly possible for the site to enable the user to:

  • Ignore eye-candy.
  • Be given a brief description of an image where it is conveys important information.
  • Provide an audio-description of a video if the sound track is insufficient.

Now let me give an example of a web site that is unacceptable. I recently booked theatre tickets for a show that includes an audio-description. It would therefore seem reasonable for a person with a vision impairment to book tickets as well. In fact, the site worked very well enabling a screen-reader user to find the show and the date, choose the seats and start the booking process, including name, address and credit card details. Unfortunately it fell down at the very last hurdle. For some reason the web designer had decided that the 'submit' button should be an image that could only be reached by a mouse click (a user who is blind could not see the button nor move the mouse to hover over it). So having done all the hard work the blind user could not submit the ticket request. The site is not only inaccessible but profoundly irritating.

Deaf

Until recently most websites were accessible to the deaf community. The written word and images are accessible. With the increased use of audio, sites are becoming less accessible. Site owners need to think about the use of audio:

  • Some of it is just ear candy e.g. background music on an intro page and can be ignored.
  • Some of it is nice to have, e.g. a welcome from the CEO, but does not contain any information, at least nothing that is not written elsewhere, a pointer to the written equivalent is all that is needed.
  • Some of it is important, e.g. The text that goes with a presentation, and in this case sub-titles (known as captioning in the web world) are required.

Having said that text is accessible it must be remembered that for many people who are deaf sign language is the preferred means of communication. A site that wants to attract and be friendly to this community may wish to consider adding a signing avatar, examples of which are now available.

Limbless

A better description would be people with muscular skeletal disorders. Depending on the specific disability the input devices include special variants of a mouse, on-screen keyboards, single switches, text prediction, voice activation etc. The design of the pages should allow interaction:

  • Without a mouse.
  • With the minimum number of keystrokes (on screen keyboards can take longer to use than a standard keyboard) .
  • Enable voice activation of controls and form input.

To better understand the importance of this consider a person who has been leading an active life and using computing and the web as a regular part of their business and private life. Now consider the same person after a spinal injury that means they now have no use of their limbs. They should be able to carry on doing everything that could do before on the computer—some of it may take longer and require more effort and concentration but nothing should be inaccessible.

Mentally retarded

This is a particularly non-PC term for people with cognitive disabilities. I was recently discussing this area and was introduced to the term 'spikey cognitive abilities' to express the idea that people have different levels of cognitive ability: reasoning, spatial awareness, memory etc.

Not all content on a site will be accessible to all users; for example a web site devoted to quantum mechanics does not need to be accessible to someone with a reading age of eight. However, the language, layout and navigation of a site should be as clear as possible to make it accessible to anyone who has an interest in the content and functionality of the site.

Multiple disabilities

The comment did not include the issue of people with multiple disabilities. Even here there are people able to use accessible web sites including blind-quadriplegics (using voice input and output) and deaf-blind users using a keyboard and Braille output.

So, in conclusion, I go back to my original answer 'Yes, ja, oui, igen' which brings up the further issue of internationalisation but that is a topic for another day.

Reader Comments

We are no longer accepting comments against this item. We suggest contacting the author directly.

23rd October 2007: 'ben' said:

I am glad to see that my comments were compeling enough to warrent a new article, but sad to see that you've still missed my point. Yes, as developers we have a responsibility to create accessable sites. A well designed site should allow people with handicaps (or differenently abled if you prefer) to be able to access and fully utilize the main functions of a site. We do this because it is right, because some of us are disabled, and becuase it makes good business sense.
However, the judge ruled that accessablility was insufficient. She is insisting that the Target developers create an _equivilent_ experience keyed for an alternate sense, not merely accessability. To go back to a point I made in response to your original article: Webpages are natively visual in design. When was the last time you put togehter a paper mock-up to test the "feel" of a layout, or had someone come in and look at your design and "read" it to you with your eyse closed? No. Webpages are natively visual and the best that can be achieved for the visually impared is a taging system to assist readers, but this is not what the judge ruled.
On an ironic note, on re-reading the ruling, I find that it violates the laws it was meant to enforce. In her ruling, the judge explicitly orders Target.com enable their site for the legally blind but does not order them to make the site accessible to ther disabilities. By making this distinction of the legally blind from other disabilities and ordering Target.com to enable their site singuarly only for the legally blind, she has seperated them out and specifically excluced other disabilities. The laws she is attempting to expand state explicitly that no person can exclude someone baised on any disability.

Reply to ben?

24th October 2007: 'Isofarro' said:

"Webpages are natively visual in design. When was the last time you put togehter a paper mock-up to test the "feel" of a layout, or had someone come in and look at your design and "read" it to you with your eyse closed?"

No. Your _design process_ concentrates on the visual aspects of the page. That in itself is not enough to warrant the statement that webpages are natively visual, as much as an elephant is just another type of wall (to paraphrase the incident of the blind men and the elephant).

A web page is built around HTML - which is a markup language that allows the author to logically structure a page. You perceive that logical structure within the confines of a browser - so one possible rendition of a logically structured document is visual, but its not the only perception. The same document can be rendered aurally by a screen reader (or even something as simple as a text-to-speech plugin).

This happens because webpages are fundamentally text in an electronic form, independent of its end intended rendering medium.

Reply to Isofarro?

30th October 2007: 'Peter Abrahams' said:

Ben
I now understand where you are coming from and hope that we really hold very similar views.
The open ended design requirements could theoretically be a problem but I suspect they will not be because the law will work in the same way as it has done with the physical world. Buildings have to be accessible under the same laws and we do not have class actions against the design of new building. Why, because there is an agreement and understanding of what makes a building accessible, this is the state we need to get to with websites. This may take some time and might even involve a few more court cases but in general this is going to have to be resolved between the disability activists and the web developers. I think it will come down to activist being happy that they can use the functions of the website in a practical way. There are so many sites (including Target when it was originally sued) that obviously do not meet this criteria. Let us get to that level on most sites and most people would be happy.

Reply to Peter Abrahams?

24th October 2007: 'Talking Books Librarian' said:

Unfortunately, I think we are a long way from having fully accessible websites to anyone with a disability. Part of this stems from the fact that some people create their own websites and do not know how to make the websites accessible. So, not only do you have companies' websites that are potentially inaccessible, but also personal websites that are not accessible. On a personal note that is less related to the discussion, I am a librarian who works with people with disabilities... I have a blog dedicated to resources for those with disabilities... feel free to check it out at http://talkingbookslibrarian.blogspot.com/

Reply to Talking Books Librarian?

30th October 2007: 'Peter Abrahams' (Author) said:

I am not disabled myself so I hope that what I am writing reflects the views of people with disabilities.So just in case anyone thinks this is nto a real problem and the solution does not have real benefits I recommend reading an article by Liz Ball who is deaf-blindhttp://www.bbc.co.uk/ouch/features/lizball_internet.shtml

Reply to Peter Abrahams?

30th October 2007: 'john brandt' said:

When I do workshops to train folks about Accessible Web Design, I stress the concept of Universal Design as the philosophy to strive for.

People in this debate tend to get stuck talking about specific disabilities and specific AT, and lose sight of the larger issue. The issue is not making the content FIT the user, but rather making the content accessible to the user.

One of the folks who responded here insists that web sites are "visual" products. In reality, web sites are tools for communicating information (i.e., content). This content comes in many forms and with many styles. The key is to separate the content from the presentational elements so everyone can access the content. And this generally means having a digital text version of all of the content - or "interpretations" of that content.

People are running around like mad these days trying to make versions of their web sites that will now be viewable on the Apple iPhone. A good web built with a philosophy of Universal Design should have no problems being displayed on an iPhone or any other non-browser device.

If we build to standards using a philosophy of Universal Design, separating content from presentation, it should create a web that is accessible to all people and to all devices.

I fully recognize that those "perfect standards" have not been completely defined. And things are always in a state of flux. So, we will need to continue to work on this.

Reply to john brandt?

31st October 2007: 'Richard Morton' said:

Apparently (I use that word as an all purpose disclaimer), British Sign Language is the fourth language in the UK after English, Welsh and Gaelic. So what? you may say. The result is that for many deaf and hearing impaired people, Sign Language is their first language, so written English is either inaccessible to them, or difficult to understand. A bit like expecting me to use a German web site, I can make out some of the words from my ancient O-level knowledge, and even gain a reaasonable understanding in some parts, but I would be very cautious about buying something for example.

What I am getting at is that is that making information accessible to a deaf or hearing impaired person isn't always as simple as putting it in writing. Something to think about.

Richard Morton
QM Consulting Ltd
http://www.qm-consulting.co.uk/

Reply to Richard Morton?

14th December 2007: 'Duncan' said:

Peter, what are your views on Web 2.0 in relation to W3 standards and accessibility. As a developer I find it cery hard to build Web 2.0 sites (Ajax) which are accessible and commply with W3C specs. Many of the Javascripts tags and methods break XHTML declarations - does this mean I should go back to HTML 4.0? Plus what are the accessibiity implications of all this client side code? Seems that you have to make two sites, one which is dumbed down for accessibility and the other which is all bells and whistles for the Web 2.0 fans. As if life as a web developer wasn't hard enough already. One final point which IDE/SDK is best for developing accessible, but attractive websites?

Thanks.

Reply to Duncan?

Advertisement



Published by: IT Analysis Communications Ltd.
T: +44 (0)203 051 5760 | F: +44 (0)870 345 9922
Email: