Who pays for Accessibility

Feb
14
2007

Are we all doing the right thing with respect to web standards, and accessibility?

Well, Nomensa recently released the full report on United Nations global audit of web accessibility. This report while only taking a very quick snap shot was damning on the application of web accessibility across the board.

The report, which has been only available as an Executive Summary since it was released on 5th December 2006, reveals that 97% of websites tested fail to achieve the minimum web accessibility level.

Now if you consider the way they measured this you may not think that it’s all that bad. They took the top sites from five sectors over 20 countries. But the sad fact is only three, yes 3 out of a 100 even obtained an A+ rating. That’s a single A, on the Web Content Accessibility Guidelines (V 1.0). These web sites (the 100) are all big business and government agencies, places that frankly have no excuse. Reminds me of the State of the web that John Allsopp conducted in 2005, except he wasn’t as damning and it was on standards compliance. Still its a sad state of affairs. We think we have come so far, when in fact its just beginning.

Who pays for the application of web standards and accessibility (yes I know they are not the same thing) , who pays for the separation of content, design and functionality.

  • Does the web design firm bare the cost and automatically retro fit standards and accessibility compliance into all it’s client web sites / CMS and web applications. Surely it’s their responsibility as they build the web site or are managing it. So they should do the convert for free, right. Why should the client have to pay for something that they can’t see any really benefit for in the outset?
  • Or does the client pay when the site has a makeover, given that maybe 2-5 years between makeovers. It’s their site after all, they own it (well the content anyway), they get the benefit from it. They should take some responsibility for the site and bare the cost in the makeover, even if it isn’t directly stated in the specification for the makeover.

This also raises the point about selling standards and accessibility.

I work on the basis that standards and accessibility compliance on new sites or makeovers is a given, its not a feature, its the baseline, the place to start. If you make it a feature it can be crossed of the list. But what happens when:

  • Firm A quotes on a site makeover, full standards and accessibility compliance, most of it will be hand coded, hourly rate is the same as Firm B. Design is basically the same. Functionality is slightly different, as it’s using a unobtrusive javascript combined with an allowance for no javascript at all by having backend scripting too as a fall back.
  • Firm B quotes on the same makeover, using automated site generation tools, no standards and or accessibility compliance (client didn’t ask, why bother doing it), Design is basically the same visually. Functionality works the same as far as the able bodied client is concerned on their computers.

Firm B, is cheaper than A, both appear to be quality firms. Firm B wins the job. Business reality – standards and accessibly loses.

End of the line, who pays for standards and accessibly compliance? The client or the web designer?

Technorati Tags: , , , ,

5 comments