Accessibility

London.gov.uk accessibility

We aim to make London.gov.uk as accessible and usable as we can for all our visitors. Read our accessible communication policy

If you have any problems using the website, feedback will give us guidance so we can make it better. If you experience any trouble accessing services or information on this site, please contact us.

If you want some support around starting to use the internet, please take a look at our helping people get online page.

For those of you needing further help on accessing websites, we hope the following information will be useful. As well as this, GOV.UK’s pages on accessibility provide a good summary of where to find out information on accessibility.

Accessibility tools

Like GOV.UK we are pointing to the BBC’s excellent accessibility pages to get you started. We’ve included some direct links below.

For further information on things like spell checking, word predicting software, keyboard stickers and voice recognition visit the BBC’s My Web My Way pages.

​​Translating our website

If you would like to view this website in another language we recommend using Google Translate - we have set the default language to Bengali on this link, to choose a new language select the drop down menu at the top-centre of the page.

Accessibility statement for London.gov.uk

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 this website is?

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

  • The neighbourhood map on ‘In my area’ pages is not accessible in several ways:
    • Users cannot interact with it via keyboard only. Neighbourhoods featured are identified as links so screen reader users will not know what the links do.
    • The map contains images on the statistics section which do not have a text alternative and a pie chart which uses colour as the only visual means of conveying information.
    • There is no text to inform users that selecting a neighbourhood will result in the statistics being updated.
  • In the London Assembly member landing pages, the different size headings displayed are not in an order that people using assistive technologies may understand.  
  • On pages which use video embedded from YouTube, the expand video link cannot be operated using the keyboard, as it does not receive focus.
  • Screen reader users are not able to read images displayed as part of the security check (Captcha) used on some forms to ensure that only human users can pass through.
  • The feedback page contains a checkbox that is displayed as part of the security check which people using keyboard navigation may have difficulty in seeing as there is insufficient colour contrast when it is accessed.
  • Some images on the website do not have a text alternative, so people using a screen reader cannot read the information.
  • Most PDF files are currently not tagged, so people using assistive technologies may not be able to understand some content.
  • For planning application listings, places of interest that are displayed with a map pin do not have a text alternative so people using assistive technologies may not be able to read the location details from the map pin. 
  • For planning application listings, places of interest that are displayed with a map are not yet fully navigable by keyboard only.
  • In the events listing pages, users are required to scroll the page horizontally to view the calendar because it is partially displayed on the initial display of the page.
  • The social media buttons for sharing a page are not correctly marked up as button elements.
  • On campaign hub pages that include the Facebook and Twitter share links these cannot be operated using the keyboard only, as they do not receive focus.
  • On some campaign pages there is a timeline carousel ‘What we have done so far’. People who use keyboard only can control this and view all the slides, but they cannot operate links on the slides. Those who have some sight but use a screenreader may find the carousel confusing, as the visual appearance gets out of synchronisation with what the screenreader says. 
  • One campaign page currently contains a video in which the information is only provided visually. Screen reader users cannot access this information because it is not provided in an alternative format such as a transcript or audio description.

What to do if you cannot access parts of this website

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

We will 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 our Digital 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.1 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 campaign pages there is a carousel of slides. People who use keyboard only can control this and view all the slides, but they cannot operate links on the slides (WCAG A criterion 2.1.1 - keyboard). We are investigating more accessible carousel design patterns to replace this.
  • Some images may not yet have a text alternative, so people using a screen reader cannot read the information (WCAG 2.1 A criterion 1.1.1 - non text content). We have been ensuring staff are trained up to do this so that as we publish new content our use of images meets accessibility standards.
  • Most PDF files are currently not tagged, so people using assistive technologies may not be able to understand some content (WCAG 2.1 A criterion 4.1.2 - name, role, value). By September 2020 we plan to fix a prioritised percentage of these, according to user need, number of downloads, whether they are required for essential services or interactions and if they are intended for users who are likely to have disabilities or impairments.
  • On the feedback form, screen reader users are not able to read the images with duplicated names that are displayed as part of the security check to ensure that only human users can pass through (WCAG 2.1 A criterion 4.1.1 – parsing)
  • The local neighbourhood map on borough pages which shows the location of places of interest has several accessibility issues, detailed below. However, we intend to redevelop this area as part of wider work which is planned for 2021. We are also investigating if we can make fixes before then.
    • The map is not fully navigable by keyboard only, as it does not receive keyboard focus (WCAG 2.1 A criterion 2.1.1 – keyboard navigation). 
    • There is no text on or above the local neighbourhood map on borough pages to inform users that selecting a neighbourhood updates the statistics so screen reader users and users with visual impairments may not be aware that such an update occurs (WCAG 2.1 A criterion 3.3.3 – labels or instructions).
    • Some images in the statistics section do not have a text alternative (WCAG 2.1 A criterion 1.1.1 – non-text content), so people using a screen reader cannot read the information.
    • There is a pie chart which uses colour as the only visual means of conveying information, so users with visual impairments may have difficulty distinguishing certain colours (WCAG 2.1 A criterion 1.4.1 – use of colour).
    • The map is not fully displayed and is displayed on screen in a fixed position when the page is enlarged, so visually impaired users cannot see the map in its entirety (WCAG 2.1 AA criterion 1.4.10 - reflow).
    • Featured neighbourhoods are identified only as links, so screen readers cannot read what the links represent (WCAG 2.1 A criterion 4.1.2 – name, role, value)

Disproportionate burden

N/A currently

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

  • On pages which use video embedded from YouTube, the expand video link cannot be operated using the keyboard, as it does not receive focus. This is third party content provided by YouTube, which is not under our control (neither funded, nor developed by us) and so falls under the exemptions of the accessibility regulations - Application, 4. (2)(e).
  • The Google reCaptcha used as a security check on some pages is not an accessible component. If the automated "I'm not a robot" checkbox test fails, it presents sets of images that cannot be navigated by keyboard or voice control, and the supplied audio alternative is usually not distinguishable even by many people with good hearing. Neither version can be used from Braille readers. Some images displayed as part of the security check also do not have sufficient colour contrast (WCAG 1.4.3. Contrast (Minimum)). This is third party content provided by Google, which is not under our control (neither funded, nor developed by us) and so falls under the exemptions of the accessibility regulations - Application, 4. (2)(e). However we plan to investigate alternative solutions to this as part of wider development work in 2021.
  • The feedback page contains a checkbox, displayed as part of the security check, which people using keyboard navigation may have difficulty in seeing as there is insufficient colour contrast when it is accessed. As this security check is third-party content which is not under our control (neither funded, nor developed by us), it falls under the exemptions of the accessibility regulations - Application, 4. (2)(e). We will however investigate alternative solutions to this in 2021 as part of a wider redevelopment.
  • On planning application listings, screen reader users are unable to read map pins that represent locations. (WCAG 2.1 A criterion 1.1.1 – non-text content). The accessibility regulations under the exemptions - Application, 4. (2)(e). do not require us to ensure maps are fully WCAG compliant, provided the information is given in an alternative format for navigational maps - and the address is also given in the page copy. 
  • The social media buttons for sharing a page are not correctly marked up as button elements. As this is a third-party widget which is not under our control (neither funded, nor developed by us), it falls under the exemptions of the accessibility regulations - Application, 4. (2)(e).
  • On London Assembly member landing pages, the hierarchy of headings is not in the ideal logical order. This has not been fixed as skipping headings does not fail a WCAG criterion and changing this currently would impact the wider site design, due to a shared component.

How we tested this website

This website has been audited to ensure compliance with WCAG 2.1 AA. A sample of pages was tested which reflected all the key user journeys for the target users of London.gov.uk. It was last retested and updated in July 2020.

All accessibility testing was done by Test Partners.

We tested:

Note: we have carried out audits across our digital estate. Related sites and/or key digital products which sit on London.gov have their own accessibility statements which you may also want to view.

Read the latest London accessibility test report.

What we are doing to improve accessibility

We carried out a full accessibility audit across London.gov.uk and are working towards achieving compliance by September 2020. Beyond that we will continue to resolve outstanding non-compliance issues that are within our control (detailed under ‘non-compliance with the accessibility regulations’). We have created a backlog of potential accessibility and usability improvements.

We are also ensuring all new work is designed and tested for accessibility throughout the build.

To help embed accessibility in our culture, processes, and policies we have carried out training for staff (content editors and designers). This is ongoing and we are currently looking at how we can support wider staff to create more accessible content – in particular, how to manage the creation of a huge number of PDF files across the GLA and the legacy content.

This statement was prepared on 6 July 2020. It was last updated on 16 July.

Team London accessibility

Rogue Landlord and Agent Checker accessibility

Healthy Schools London accessibility

Newsfeed accessibility

Healthy Early Years London accessibility

Small Sites accessibility

Non-Road mobile machinery accessibility

Share this page