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   

Typical Government Response? Yup.

A recent government epetition read:

“We the undersigned petition the Prime Minister to ensure that any website launched by the government complies with accessibility standards (WCAG AA at least).”

The response?

“The Government is committed to ensuring that all government websites are accessible and easy to use for people with disabilities.

Action 7 of the Prime Minister’s Digital Strategy is to ‘improve accessibility to technology for the digitally excluded and ease of use for the disabled’.

This strategy is to be implemented by DTI with support from OGC and eGU (now the Cabinet Office Delivery and Transformation Group). A cross-government review of the Digital Strategy is currently under way under the supervision of the DTI).”

Firstly, how is this responding to the petition? And given that this petition came about because of the perceived failure of the DTI to get its house in order with regards web accessibility, what do we think about their ability to implement and supervise this?

Or have a totally mis-read this reply. Please tell me I have!

The epetition text, right here …

Comments (5) left to “Typical Government Response? Yup.”

  1. Matt Round wrote:

    The governments web projects I worked on in my former day job weren’t perfect but always had to meet the required accessibility standards, which was sometimes quite frustrating, as we’d see larger IT consultancies getting away with delivering sites with horrendous code and scripting/browser dependencies. The rules certainly weren’t enforced consistently.

  2. Toni Ruckwood wrote:

    I too signed the petition and got the email reply you’re talking about.

    Unfortunately, you did read it right. You did’nt really expect a straight answer from a politician did you?

  3. dotjay wrote:

    They took long enough to reply to the petition - it took a few weeks after the petition closed - and their response didn’t address the main point of the petition: to ensure that future implementations are actually accessible. The current strategies are obviously not good enough, else the problematical DTI website would never have come about.

  4. dotjay wrote:

    I’ve posted further thoughts over on my blog:
    Government responds to website accessibility e-petition

  5. Bob wrote:

    Yep, I signed up too and received a somewhat dismissive and typically sidestepping politician’s reply. Very poor, but what can one do, even collectively? Perhaps they’d pay attention if someone were to sue for being discriminated against by exclusion.

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