I just went through some sites for an accessibility audit and keep bumping into the same issue: Alternative text for the sake of alternative text. If I surf some pages with a text browser, IBM Homepage Reader or Jaws and it takes me 10 minutes more to find my way around, I start wondering where the common sense was when the site was created or who was the main target for these alternative texts. Take this gem taken from a noscript block:

We use javascript to write a “breadcrumb” here. If you want to view it you need to enable scripting in your browser. If this is not an option for you, you can navigate easily and in an equivalent way, by modifying the address of the page that you are viewing. For example: if the address shown is http://www.example.com/section1/a_and_b/c_and_d.html – you can change this to http://www.example.com/section1/a_and_b.html to navigate to the previous page in the hierachy or to http://www.example.com/section1.html to navigate to the top page in the hierachy.

They forgot to mention that I can also go to their competitors site, who didn’t bother using JavaScript to generate breadcrumbs, and offers me three easily understandable links.

Another issue is that a lot of developers rely on title attributes to deliver crucial information, like “PDF Document” or “opens in new window”, and not all who use assistive technology do have title reading enabled. Some even get rid of it by default, and who could blame them when you get titles like “Click to skip to content (skips navigation)” for a “Skip to content” link and a “click to visit the xyz page” for links stating “xyz”?

Generally, there are some sins I try to avoid:

• Alternative text that is dependent on the image/effect
• Alternative text that is overly elaborate – think of explaining something over the phone, not read out a manual
• Needless repetition of text. A link is a link, no need to repeat that (My favourite was “link to www.example.com – click to activate – opens in new window” as a title).

The sites with the best usability are the ones that helped us reach our visit goal without realising how the site helped us. As soon as you need elaborate explanations it is a sign that you either broke a convention or your interaction steps to reach the goal are simply too complex.

To anybody arriving here via “graphic images london bombs” in Google: What is wrong with you?

I left the house at 8am, and wanted to get to work in time. I crossed Kings Cross probably 10 minutes before the Explosion and got evacuated at Victoria. 50 minutes bus ride later I arrived at the office at 10:20 just to hear that the workshop I had to hold got cancelled. Now I am stuck here and don’t see much chance to get home tonight (south west to north east). And some lowlife spams me with comment spam. Cheers.

And that after all the happy news yesterday. The olympic games are coming, software patents got fought off and the crazy frog gets it in the netherlands .

Update
I am deeply touched by all the emails, text messages and instant messages coming in asking if I am alright.
This is what is important right now, not how many people are dead and injured, where you can find the most graphic pictures and who did it. There is a reason for terrorism, and fighting terrorism is protecting us, but it is fighting a symptom, not a cause. There is also no protection against terrorism. You can do a lot, but there is no way to prevent people from killing other.
It seems causing harm to one another is one of the parts of the human psyche where we are the most inventive. In the middle ages people were unable to read or write but they knew how to torture people and how to create weapons that maim the most.
I don’t want to sound like a hippie, but caring for another and enjoying life and getting on with life is the most important thing right now. I just came back from the shops as I had to buy some clothes to wear tomorrow (I am staying in a company flat nearby) and on my way here I saw a bunch of kids driving their small scooters through a fountain and giggling like mad when they got splashed. It may be a trivial sight, but the innocence and carelessness of it was wonderful to behold. It is not us terrorists fight, it is what we supposedly stand for. Do not let them turn us into bad people full of hate, cause this will mean they have won.

Aspiring athletes can book a place to put their sleeping bag in my flat now. £250 a night, no breakfast included.
At least that will mean we can use the Dome for something again, depending that it still stands then.

As a part of my job I am right now conducting an accessibility audit of one of our clients’ sites. My findings so far and the background and history of the project are a perfect example of how much of a gap is between accessibility best practice tutorials / articles and the real business world.

The Project

• We have developed and maintained the site since 2001
• We are only partly responsible for the design and the content. A design agency delivers all of that – with focus on print and TV.
• It is a maintenance project on a monthly budget that includes all deliveries – from content maintenance (image optimization) to server infrastructure and hosting
• To keep within budget, the maintenance development is outsourced to an office outside the UK with a quick turnover in developers of a wide range of skills and quality awareness

The client expectations and attributes

• The site should show the brand and be “fun to use”
• The client is not dependent on the site as a main customer channel – it is a worldwide known brand and has real outlet stores.
• The site does not have any products for sale or order; it is simply another communication channel to show the brand

The technical background

• The technical implementation was initially ASP with some database functionality for lookups and was optimized to work for IE4 and Netscape Communicator 4.x. All the interactive sections like signing up for the newsletter, download of fun wallpapers, screensavers and other brand collateral is still in this format and just got a new lick of paint in between.
• About two years ago, the client wanted to go Flash, but have an HTML fallback option. Both should be maintained from the same source, and there should not be any overhead or extra work for the HTML version. This is achieved by using XML for the content, XSLT to generate the HTML and Turbine to generate the Flash on the fly. The live site is generated statically by Cocoon.
• As interaction with a database was out of budget and scope, all the earlier mentioned server-interaction sections are opened in pop up windows.
• As the Flash version is the “fun to use” one the site as it is now automatically sends users with Flash enabled to that one – rendering the HTML version as an “accessible” version rather inaccessible for users with special needs and Flash.

Enter “Accessibility on a shoestring”

As the brand is constantly in the limelight and also gets a fair amount of flak, and with some gentle prodding of yours truly, the client got aware of accessibility needs and demanded “some of that”.

In an initial presentation I tried my best to point out that accessibility is more than just some technical changes to the HTML, introduced different kinds of disability and showed sections of the page that are inaccessible by trying to use them with a keyboard and speech recognition.

Aware of budget restraints, I came up with three options to tackle “the accessibility problem” (they were named differently though):

• COA (cover our a…. you know): Get rid of the automatic redirect and offer the user a choice between a Flash version – that might not be accessible to all – and a more basic HTML version that is accessible. Offer a mean of contact on each page to tell the client about issues and offer an accessibility statement explaining why some parts of the site are not accessible.
• Clean Up: All of the COA and changing the forms not to appear in pop-ups any longer.
• Face Facts: Embracing the fact that most of the site is not necessary content but advertising, we split the site into “brand experience” and “business” sites, where the former can be as flashy as they come and the latter easy to use and fully accessible.

Needless to say, the budget demanded COA only, and after another brand session the client decided not to have a landing page that allows the user to choose between Flash and HTML but offer a small link to the HTML version on the Flash site.

So here are the facts:

• The site content is brand orientated, most text provided only makes sense when you can see the imagery that comes with it or there is simply no text but only visuals.
• These visuals and any content has gone through a painstaking and expensive approval process, and the client won’t be happy for us to tell we cannot use it for an accessible version.
• Anything we come up with as extra for the accessible version (information text, alternative texts, changes to “click here” and “choose on the right” wording) has to go through the same approval processes.
• The client does not want to spend extra time and money on the accessible version and relies on us to do the right thing. We get paid as the delivery agency and there is no need for them to get someone involved in accessibility.
• As part of the Flash/HTML redesign was us telling the client there is no extra work involved, it is tough for us to say, “Well there is more work involved now”

Now tell me: How many tutorials, best practice and information articles about accessibility have you seen that help in this case – and it is not a singular case, a lot of design oriented agencies and those who have to rely on third party content face the same issues.

We got the bloggers, and brochureware small to medium business web site owners, now it is time to think about how to make business aware of what accessibility encompasses. And no, there is no such thing as “Accessibility does not affect design”, unless the original design is developed with diversity in mind.

Maybe it is time to stop advocating accessibility as an easy to achieve goal, and a technical problem that can be tackled independently from the other layers involved.
It is a state of mind, a way to design and write that anyone can benefit of.

Products developed with limitations in mind have given designers a new perspective and resulted in innovation. Thomas Edison developed the carbon transmitter (microphone) for Bell’s telephone because he had trouble hearing its faint sounds. On his invention of the phonograph, Edison explained: “Deafness, pure and simple, was responsible for the experimentation which perfected the machine.”
From Innovative Design Inspired by Accessibility

Digital Web will release an article of mine on the 20th called “10 reasons why our clients don’t care about accessibility” with more examples like this one.

For an upccoming release , that should reach as many CSS fans as possible, I’d like your help and tell me which CSS, Web Standards or JavaScript related web zines you frequently read?

Personally, mine are:

• Alistapart
• Digital-Web
• and Sitepoint

Which ones would you add?