Does this page look plain and unstyled?

Tools, wizards, articles and tutorials on Web Accessibility for the conscientious web developer

Subscribe to Accessify's RSS Feed   

Government Web Site Failure - Is It So Shocking?

Yesterday the BBC reported on a study released by Southampton University in the UK that found a 60% failure rate in UK government websites where standards compliance is concerned. Since that report on the BBC I’ve noticed a bit of commentary on it and received a few emails along the lines of "have you seen this?" from shocked individuals. The biggest shock for me is, frankly, that people are shocked and surprised at all.

The BBC report certainly highlights an important issue but it also blurs some important points when it says:

"Some 60% of UK government websites contain HTML errors"

Then it later quotes the author of the study as saying:

"Although 61% of sites do not comply with the Web Content Accessibility Guide, the 39% which do is encouraging."

Is the 60% failure figure one of HTML validation issues, as the first quotation above suggests, or is it a 60% failure in terms of accessibility pass/fail ratio? If it’s the latter, this is a little more worrying. As for the former, well, we all want the sites to use to validate, but with the general mush of various layers of in-house web development, outside agency involvement and hideously bad content management systems (CMSs), quite honestly I’d be amazed if the validation rate were anything even close to 40%.

For my money, this story tells me largely what I suspected about UK government sites (but couldn’t be bothered to go out and collate the figures for myself). The best part of the story, I think, is the finishing quote from an anonymous

’spokesman for the Cabinet Office’:

“One difficulty is that many authoring tools do not generate compliant HTML and make it difficult to edit the coding … This is an issue that the IT industry must address and we are working with them on that.”

It’s refreshing to see a government official correctly identify that the authoring tools are often to blame here (cough, ATAG, cough!) . But just who is ‘them’ in that sentence and who are the ‘we’ in that sentence (given that the source is unnamed). If you have any further light to shed on this story - specifically about what those figures actually relate to - and also what action is being alluded to towards the end, I’d love to find out (use the comments please).

This post has been cross-posted at webstandards.org - please add any comments there

.

Post a Comment

(Never published)
 

Site Navigation

Outside reading

Migrating from WCAG 1.0 to WCAG 2.0
Roger Hudson provides a through transition guide from WCAG 1 to WCAG 2
Beyond CAPTCHA: No bots allowed
James Edwards (aka Brothercake) provides a useful run-down of the problems posed by using CAPTCHAs
Jeremy Keith does an excellent write-up of the Accessibility 2.0 conference (which I was unable to attend)
Sharepoint and Web Accessibility
Bruce Lawson describes the disparity between Sharepoint/MOSS developed web sites and the level of accessiblity that the tool offers to users (summary - it really is not good!)
How does a screen reader user really hear your web site?
Interesting post on Beast Blog about how a screen reader user - a real one! Not one of those fake web developer tester types! - uses the tool to read a web page. A few surprises were waiting in store for author Mike Cherim.
Web Accessibility Toolbar now available in simplified Chinese
The Web Accessibility Tools Consortium (WAT-C) release a simplified Chinese version of the Web Accessibility Toolbar.
Web 2.0 vs Web Accessibility
1-day seminar in London, 25th April, brings together experts in the field to discuss/demonstrate the accessibility issues faced by web 2.0.
Leading accessibility technologists form new alliance to fix problems
The Accessibility Interoperability Alliance (AIA), comprising (among others) Adobe, HP, Microsoft, Novell, and from the assistive tech industry Dolphin, GW Micro and HiSoftware forms to work together "to create and harmonize standards for accessible techn
Fieldsets, legends and screen readers
An excellent run-down of how fieldsets and legends can improve accessibility and how the various screen readers cope with this useful markup.
CAPTCHAs explained - WacBlog
Another really good post on the RNIB\'s Web Access Centre blog explaining captchas, why they\'re bad for accessibility and what the alternatives may be.
Making WCAG easier to read
Derek Featherstone has created some fancy style sheets to make reading WCAG documents a little easier on the eye.
Top Tips for the title attribute
Ann McMeekin provides a set of simple tips regarding when - or rather when not to - use the title attribute. \'Cos sometimes you can try *too much* to be helpful
California court tilts towards mandating web accessibility
Outlaw.com reports (on behalf of The Register) on the Target California class action lawsuit, digging a little deeper into what Target have been doing of late to address matters.
Screen Readers and display:none
Juicy Studio, aka Gez Lemon, investigate some quirks whereby screen readers announce content that they should not be. Perhaps this could be used for good rather than evil?
Google Developer Podcast: The status of accessibility on the Web
An interview with Google research scientist TV Rahman (and Hubbell, his seeing-eye dog!). Lots of talk about CAPTCHAs and accessibility, but no sign of a transcript for this interview as yet.

View all Accessify bookmarks on del.icio.us



This page is styled using Cascading Style Sheets (CSS). If you can read this message, the chances are that your browser does not properly support CSS or you have disabled this yourself. The content on this site is perfectly readable without style sheets, though; it just doesn't look quite so fancy.

site statistics

This site is partnered with MIS Web Design and Top4Office for Copiers and Digipro for Photocopiers. Web design by Swindon Internet & PR Services.

How you can help support this site: Learn web design from the creator of this site, or help him by requesting some PR Photography