Accessibility statement for Data for London

This accessibility statement applies to the public-facing Data for London website. It does not cover any subdomains and other content.

This website is run by the Greater London Authority (GLA). We want as many people as possible to be able to use this website. For example, that means you should be able to:

change colours, contrast levels and fonts
zoom in up to 400% without the text spilling off the screen and without content being truncated or overlapping
navigate most of the website using just a keyboard
navigate most of the website using speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We've also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible is this website?

We know some parts of this website are not fully accessible:

Some landmark regions are missing or used inappropriately. Screen reader software users are encouraged to use a different method to navigate within pages.
Headings have been used, but have not been nested according to specification. Screen reader software users should still be able to navigate within pages using the headings keyboard shortcut.
On a limited number of pages, it may not be clear what the current location is from the secondary navigation and page title.
On some pages, there is no mechanism to bypass the links in the header. Keyboard users can TAB through the limited number of links there, and screen reader software users should use an alternative in-page navigation technique to jump to the main content.
On the search page, the visible label of the search input element does not match the accessible name. Voice recognition software users should use an alternative approach to send focus to the search input.

Feedback and contact information

We're always looking to improve the accessibility of this website. If you find any problems, think we're not meeting accessibility requirements, or need information on this website in a different format (like accessible PDF, large print, easy read, audio recording or braille) then please Call 0207 983 4000 (Monday to Friday, 9am-5pm)
Get in touch via our online form
Email [email protected].

We'll consider your request and get back to you within five working days, to advise further.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations'). If you're not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

The Greater London Authority is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content). We plan to add text alternatives for all images by September 2025. When we publish new content, we’ll make sure our use of images meets accessibility standards.
Some landmark regions are missing or used inappropriately. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to fix these issues by September 2025.
Headings have been used, but have not not been nested according to specification. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to fix these issues by September 2025.
On a limited number of pages, it may not be clear what the current location is from the secondary navigation and page title. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to fix these issues by September 2025.
On some pages, there is no mechanism to bypass the links in the header. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks). We plan to fix these issues by September 2025.
On the search page, the visible label of the search input element does not match the accessible name. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name). We plan to fix these issues by September 2025.
The follow / unfollow control is functional rather than navigational, and the role should be identified as a button not a link. In addition, the state of the control is ambiguous. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value) and WCAG 2.2 success criterion 4.1.3 (Status Updates). We plan to fix these issues by September 2025.
A small number of text components do not have sufficient contrast with the background colours. This fails WCAG 2.2 success criterion 1.4.3 (Colour Contrast). We plan to fix these issues by September 2025.
A small number of non-text components do not have sufficient contrast with the background colours. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast). We plan to fix these issues by September 2025.
html5 validation has been used for error handling on the create account, login and reset password forms. This fails WCAG 2.2 success criteria 2.2.1 (Timing Adjustable) and 3.3.1 (Error Identification). We plan to fix these issues by September 2025.
It may not be clear which input elements are required and which are optional on the create account, login and reset password forms. This fails WCAG 2.2 success criteria 3.3.2 (Labels or Instructions). We plan to fix these issues by September 2025.
When viewed at 400% with the browser width set to 1280px, when the navigation menu is expanded, access to the main menu is restricted. Navigation items are outside of th viewport and no vertical scrolling is permitted to view the content. This fails WCAG 2.2 success criteria 1.4.10 (Reflow). We plan to fix these issues by September 2025.

Disproportionate burden

Documents (PDFs) on the London Datastore

We have assessed the time and cost of making PDFs and other document types accessible, including those published since 23 September 2018, and believe updating all of these would represent a ‘disproportionate burden’ considering the resources currently available to the GLA and how infrequently the documents are accessed. All future GLA PDF reports will be designed to meet accessibility requirements.

Preparation of this accessibility statement

This statement was prepared on 30 January 2025. It was last reviewed on 08 May 2025.

This website was last tested on 08 May 2025. The test was carried out by Test Partners Ltd

We used this approach to deciding on a sample of pages to test:

We followed GOV.UK guidance on deciding how to check the Data for London website as follows:

We used an automated website mapping tool to identify all the pages and documents on the website.
We removed all the documents from the list.
We grouped the remaining pages according to type.
We manually assessed a number of pages from each group to determine the level of consistency within the group and the type of content on those pages.
We manually assessed all the “unique” pages such as the home page to determine the type of content on those pages.
We identified a minimum representative subset of pages that contain examples of the most common layouts, components and features, including:
1. The header and footer.
2. Important “unique pages”.
3. Pages with text content and data tables.
4. Interactive elements such as forms, tabbed interfaces, hide / reveal functionality and content filtering.
We conducted a manual WCAG audit on the representative subset of pages.
We conducted two rounds of fixing and retesting, such that most WCAG non-conformances have been fixed.
We will conduct further rounds of fixing and retesting until all the WCAG non-conformances have been fixed.