Accessibility statement for Talk London

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 300% without the text spilling off the screen
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 it this website?

This site has been built to be as accessible as possible and tested against WCAG 2.2 AA. There are some areas which are not yet fully accessible:

On some forms, asterisks are used to show where input is required. These characters are redundant for screen reader software users, and should be hidden.
On some forms, the error summary is incorrectly identified as a footer element.
On the first form in the registration process, there is a typo that means that the Close button on the “Why do we need this?” pop-up does not have an accessible name.
On the third step of the registration process, the Borough autocomplete component only makes an announcement when the first letter is typed, and not for subsequent letters.
On the second step in the registration process, when an error is made focus is not sent to the error summary component. Users are encouraged to manually check the error summary above the form.
On the second step in the registration process, if some of the input elements are accidentally left blank, then there may not be an error message. If there are problems, check that all the fields that require data are not empty.

Low vision users

On some forms, individual error messages are not persistent under certain conditions.
A small number of text elements may be difficult to read for low vison users due to insufficient contrast between the text and the background colour.

Keyboard-only users

On forms with information panels, there is not sufficient contrast to see keyboard focus on the Close control.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

call 020 7983 4000 (Monday to Friday, 9am - 5pm)
get in touch via our online form
or email [email protected]

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

If you cannot view the map on our contact us page, please call or email us for directions.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact the Talk London Team by emailing [email protected].

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’) in England, Wales and Scotland. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Contacting us by phone or visiting us in person

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Find out how to contact City Hall.

Technical information about this website’s accessibility

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

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

On some forms, asterisks are used to show where input is required. These characters are redundant for screen reader software users, and should be hidden. This fails WCAG 2.2 success criterion 1.1.1 (non-text content)
On some forms, the error summary has a role=”contentinfo” attribute, incorrectly identifying it as a footer element. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships)
On the second step in the registration process, some input elements are missing required autocomplete attributes. This fails WCAG 2.2 success criterion 1.3.5 (identify input purpose)
On some forms, individual error messages are not persistent under certain conditions. This fails WCAG 2.2 success criterion 3.3.1 (error identification)
On the second step in the registration process, when an error is made focus is not sent to the error summary component. This fails WCAG 2.2 success criterion 2.4.3 (focus order)
On the second step in the registration process, if some of the input elements are left blank, then there may not be an error message in text. This fails WCAG 2.2 success criterion 3.3.1 (error identification)
On the first step in the registration process, there is a typo that means that the Close button on the “Why do we need this?” pop-up does not have an accessible name. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value)
On the second step in the registration process, a <fieldset> element has an “aria-required” attribute, which is not allowed on this element. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value)
A small number of text elements do not provide sufficient contrast. This fails WCAG 2.2 success criterion 1.4.3 (colour contrast)
On forms with information panels, there is not sufficient contrast to see keyboard focus on the Close control. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast)
On the third step of the registration process, status messages for an autocomplete component are only partial. This fails WCAG 2.2 success criterion 4.1.3 (status messages)

Disproportionate burden

Talk London is planning to fix all the issues we have so far identified in testing.

Content that’s not within the scope of the accessibility regulations

Talk London does not have any content that is beyond the scope of the accessibility regulations.

How we tested this website

This website relaunched in March 2021. It was built to comply with WCAG 2.1 AA and was tested against this throughout the build. This means that rather than specifying a sample of pages to test, all the new content types (templates) and key user journeys were tested as they were developed. The last full audit was in June 2023.

It was tested in June 2024 against the new WCAG 2.2 Success Criteria.

All accessibility testing was done by Test Partners.

We tested the Talk London site, available at /talk-london

This accessibility statement reflects the last test from October 2025.

This statement was prepared on 09 April 2021. It was last updated on 23 January 2026.

What we’re doing to improve accessibility

We have resolved all outstanding non-compliance issues that are within our control (detailed under ‘non compliance with the accessibility regulations’). 

We are planning further accessibility testing of the site, including new features that have been developed and rolled our since the site was relaunched in March 2021.

We are training staff (content editors and designers) to ensure new content we create adheres to accessibility and usability standards. 

This statement was prepared on 09 April 2021. It was last updated on 03 April 2024.

Share this page

Share via email

Need a document on this page in an accessible format?

If you use assistive technology (such as a screen reader) and need a version of a PDF or other document on this page in a more accessible format, please get in touch via our online form and tell us which format you need.

It will also help us if you tell us which assistive technology you use. We’ll consider your request and get back to you in 5 working days.