Get an air pollution assessment documentation

Information about the service

Accessibility Statement ​

This accessibility statement applies to https://get-an-air-pollution-assessment.service.gov.uk. This website is run by DEFRA. 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 ​

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

  • some page titles do not describe the topic or purpose of the page
  • the keyboard focus order is illogical
  • some interactive controls are missing labels
  • instructions rely on visual characteristics
  • some instructions rely solely on visual characteristics
  • some text does not meet minimum colour contrast requirements

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:

We’ll consider your request and get back to you in 2 days.

Contacting us by phone ​

We do not provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment, but we aim to respond to emails within 2 working days.

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 us. Our product management team will triage your feedback and incorporate, as appropriate, into our product development cycle of ongoing software changes.

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 ​

DEFRA 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 not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content ​

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

Non-compliance with the accessibility regulations ​

  • Across multiple pages, non-text content does not have a text alternative. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to review this by May 2027 and resolve if possible

  • Images are used as labels for multiple components and do not provide appropriate text alternatives. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to review this by May 2027 and resolve if possible

  • Custom controls are used for multiple elements instead of semantic markup. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to review this by May 2027 and resolve if possible

  • Multiple labels are not correctly associated with the corresponding user interface components. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Visual headings are not conveyed through semantic markup. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Semantic markup is not used appropriately for layouts. Associated content is presented visually and may not be clear to users of assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Semantic markup is not used correctly for disabled components. Disabled menu items do not expose a role, meaning their disabled state is not announced and they are read as plain text by screen readers. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Several buttons open new panels of information, but the boundaries of these panels are not defined. As a result, screen reader users may not realise new content has appeared, may struggle to locate it, and may find it difficult to understand how it relates to the rest of the page. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Tables are present which are not marked up using semantic markup, meaning that table structures may not be programmatically determinable. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Tables are present which use semantic markup and ARIA labels. The table header elements have been given button roles, which means that table structure information may be lost for some users of assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • In many components, state information is conveyed through presentation and is not programmatically determined or available in text. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to review this by May 2027 and resolve if possible

  • Instructions and error messages rely on sensory characteristics of components and are not fully conveyed in a non-visual way. This fails WCAG 2.2 success criterion 1.3.3 (sensory characteristics).

We plan to review this by May 2027 and resolve if possible

  • Colour is used as the sole method to convey information. Specifically, colour alone is used to indicate differences between figures such as percentages. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

We plan to review this by May 2027 and resolve if possible

  • Text relating to unit measurements does not meet contrast requirements. This fails WCAG 2.2 success criterion 1.4.3 (contrast(minimum)).

We plan to review this by May 2027 and resolve if possible

  • Content cannot be increased in size without loss of information or requiring scrolling in two dimensions. This fails WCAG 2.2 success criterion 1.4.10 (reflow).

We plan to review this by May 2027 and resolve if possible

  • User interface components within graphs do not meet contrast requirements. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

We plan to review this by May 2027 and resolve if possible

  • Content triggered by pointer hover and keyboard focus becomes visible and then hidden, obscuring other content. There is no mechanism to dismiss this content without moving pointer hover or keyboard focus. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).

We plan to review this by May 2027 and resolve if possible

  • Not all functionality is available using keyboard-only controls. Specifically, panels cannot be resized and tooltips cannot be triggered. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).

We plan to review this by May 2027 and resolve if possible

  • There is no mechanism to bypass repeated blocks of content across multiple pages. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).

We plan to review this by May 2027 and resolve if possible

  • Across multiple pages, page titles do not describe the topic or purpose of the page. This fails WCAG 2.2 success criterion 2.4.2 (page titled).

We plan to review this by May 2027 and resolve if possible

  • The focus order is illogical across webpages. Activating navigational links automatically moves focus to the main page content. When context changes occur, focus does not return to the next logical element. Additionally, non-interactive elements are unexpectedly focusable. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

We plan to review this by May 2027 and resolve if possible

  • Focusable components do not receive focus in an order that preserves meaning and operability. When overlays are displayed, focus is not moved to the content. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

We plan to review this by May 2027 and resolve if possible

  • Visually hidden content can receive focus via assistive technologies such as screen readers. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

We plan to review this by May 2027 and resolve if possible

  • Labels on multiple buttons do not sufficiently describe the topic or purpose of the content. This fails WCAG 2.2 success criterion 2.4.6 (headings and labels).

We plan to review this by May 2027 and resolve if possible

  • A visible focus indicator is not consistently present across all components and does not meet contrast requirements on some focused elements. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).

We plan to review this by May 2027 and resolve if possible

  • Several components have an accessible name that does not include the visible text or adequately convey the visual content. This fails WCAG 2.2 success criterion 2.5.3 (label in name).

We plan to review this by May 2027 and resolve if possible

  • Dragging movements are required. Specifically, dividers used to adjust the size of on-screen content cannot be operated using a single pointer. This fails WCAG 2.2 success criterion 2.5.7 (dragging movements).

We plan to review this by May 2027 and resolve if possible

  • Changing the settings of a user interface component automatically causes a change of context without informing the user of this behaviour prior to use. Specifically, when the value of the select component is changed, the form is submitted automatically. This fails WCAG 2.2 success criterion 3.2.2 (on input).

We plan to review this by May 2027 and resolve if possible

  • Multiple form fields either do not have an accessible name, or the text label describing the expected input is not persistent. This fails WCAG 2.2 success criterion 3.3.2 (labels or instructions).

We plan to review this by May 2027 and resolve if possible

  • There are multiple user interface components where the name and role are not programmatically determined, or where changes to state, properties, or values are not communicated to assistive technologies. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to review this by May 2027 and resolve if possible

What we’re doing to improve accessibility ​

Our accessibility roadmap ties into the development cycle of the service itself, where we plan to be rolling out the service to the whole of the UK, and we aim to have addressed as many as possible of the accessibility non-compliances by then.

Preparation of this accessibility statement ​

This statement was prepared on 29/04/2026. It was last reviewed on 01/05/2026.

This website was last tested on 30/08/2024. The test was carried out by DAC.

DAC tested the service based on its core functionality and primary user journeys.