October 2007 Archive
October 18, 2007
FOI enquiry - withdrawal of .gov.uk domains
As part of the preparation for my talk at Techshare earlier this month I made an FOI enquiry to the COI on 15th September about the conditions of use for .gov.uk domains.
I have a question about the conditions of use for .gov.uk names, which appear on the Cabinet Office at http://www.cabinetoffice.gov.uk/government_it/web_guidelines/domain_names.aspx
These conditions state in section 4 that websites which do not comply with current UK disability legislation will have their domain names withdrawn. Other circumstances when .gov.uk domain names may be withdrawn are also detailed.
Could you please tell me:
- How many .gov.uk domains have been withdrawn during the lifetime of these conditions for failure to comply with disability legislation.
- How many .gov.uk domains have been withdrawn for other reasons listed in the conditions.
To give a little more context, Section 4a of the conditions of use state:
The applications (Web, email, etc) using a .gov.uk domain name must comply with current UK legislation and support channels that provide accessibility for disabled people, members of ethnic minorities and those at risk of social/digital exclusion. Legislation includes Copyright, Data Protection Act and Disability Discrimination Act. Abuse of will result in the name being withdrawn.
Today I received this response from the COI:
Firstly, it is important to understand the legislative context and the guidance for compliance with it. In your letter you state in relation to the conditions of use of a .gov.uk domain name that, 'websites which do not comply with current UK disability legislation will have their domain names withdrawn.' This isn't the case for a number of reasons. Firstly, we are not just looking at whether a website complies with disability legislation, we are also looking at whether a website meets the minimum standards for accessibility. The guidelines state that websites should 'comply with the accessibility recommendation for public sector sites, that is, W3C WAI Level AA.'
Secondly, it should be stressed that disability legislation is in place to protect the rights of the individual, not to detail the specific requirements on websites (both within and outside the .gov.uk namespace). Even if websites meet the recommended minimum standard, this is no guarantee that the user experience for people with disabilities will be problem free. This fact was highlighted in the formal investigation carried out by the Disability Rights Commission and re-iterated in the 2005 survey of public service eAccessibility commissioned by the Cabinet Office.
Thirdly, the guidelines go on to say that, 'Failure to comply with this may result in the name being withdrawn.' This implies that websites will be considered for withdrawal if they fail to meet the minimum standard, not automatically withdrawn.
Having said that, the Government has been working with industry, academia and the third sector to build a robust approach to delivering inclusive websites. To ensure that government pays due regard to current disability legislation (the Public Sector Disability Equality Duty) and in order to meet European objectives for inclusive e-government (Riga Ministerial Declaration 2006), COI has updated Chapter 2.4 of the Guidelines for UK Government Websites and proposes that all government websites must meet Level Double-A of the W3C guidelines by December 2008. The updated guidance has recently been sent out for formal consultation and is attached for your information.
In answer to your question,
- No website domain names have been withdrawn for failure to comply with disability legislation; and
- No website domain names have been withdrawn for the other reasons set out in the conditions of use.
However, the government has taken a proactive approach to reducing the overall number of websites it owns and in the future we can expect to see increased focus on raising the standards for government websites, including inclusivity and accessibility. This is part of the Transformational Government Strategy to converge websites around audience channels including Directgov and BusinessLink. This will be reflected in the updated policy on naming and registering websites, which will go for formal consultation later this month.
The most telling part of the response for me is that the conditions of use for .gov.uk domains have never been enforced. Given that section 4a explicitly states that sites not complying with current legislation will have their name withdrawn, one can only conclude that the agency responsible for upholding the conditions considers every website ever to be published under a .gov.uk domain to be compliant with current UK legislation around accessibility. (Or am I being unduly harsh and literal?) More support for the view that the proposal in Delivering Inclusive Websites to use WCAG as a measure and domain withdrawal as a consequence is a waste of time and needs to be replaced with a more positive and realistic scheme?
Perhaps more revealing of the government's future strategy is the final paragraph, which refers to the reduction in the number of government websites and an increased focus on raising standards. It's likely that the recently issued consultation around web accessibility is a thinly disguised ploy to encourage as many .gov.uk sites as possible to move into the loving arms of DirectGov, or at least onto the technical platform it now shares with several other large, high profile departmental sites. If it happened it wouldn't be a bad thing.
October 5, 2007
Today I had the pleasure of presenting at Techshare . I saw some great talks, made a lot of new friends, saw a lot of old friends and my presentation seemed to go down well.
My presentation, "Influencing government web accessibility policy: advocacy vs. militancy", is now on the site and available to download with speaker notes:
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