New UK government web accessibility consultation
On Tuesday the COI (Central Office of Information) released a consultation document titled "Delivering inclusive websites: user-centred accessibility". The document isn't yet available online, but I'm told it should be on the Cabinet Office site from some time next week.
The main thrust of the document is that all existing UK government websites should be accessible to WCAG level AA by end December 2008, while all new sites should be conformant before being launched. The main difference between this policy target and the endless procession of missed targets we've seen over the past few years is the explicit threat of the withdrawal of the .gov.uk domain for sites which fail to meet the standard.
The COI (and the Cabinet Office before them) already have this power under the Code of Practice for .gov.uk domains (see Where are the gatekeepers, March 2006) but as far as I know have never exercised it. Whether the threat is real this time remains to be seen.
But it is only a consultation document at this stage, and it's a prime opportunity to lobby the government to adopt a robust stance over non-compliance. If anyone wants a copy of the document please email me and I'll be happy to pass it on.
Here's the text that accompanied the document:
The Central Office of Information (COI) would like to invite you provide feedback on the attached document, Delivering Inclusive Websites (TG102), by end of business November 13, 2007.
This guidance is an update of Chapter 2.4 of the Guidelines for UK Government Websites http://www.cabinetoffice.gov.uk/e-government/webguidelines/
In order to meet European objectives for inclusive e-government and so that the UK public sector meets its obligations with regards to disability legislation, we have stipulated that all government websites must meet Level Double-A of the W3C guidelines by December 2008. Failure to satisfy this requirement will result in initiation of the process to withdraw the .gov.uk domain name used by the website.
Government websites are strongly recommended to develop an accessibility policy to aid the planning and procurement of inclusive websites. This includes building a business case, analysing user needs, developing an accessibility test plan and procuring accessible content authoring tools. The guidance covers some of the design solutions to common problems faced by users but is mainly aimed at strategic managers and project managers to assist with planning and procurement.
Please send comments to email@example.com