Accessibility statement for UK AIR

This accessibility statement applies to https://uk-air.defra.gov.uk, UK AIR.

This website is run by the UK Department for Environment, Food and Rural Affairs (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 using browser or device settings
  • zoom in up to 300% without the text spilling off the screen, though there may be some elements that do not work as expected at higher zoom levels
  • navigate most of the website using a keyboard or speech recognition software
  • listen to most of the website using a screen reader

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

How accessible this website is

We know parts of this website are not fully accessible. Many users will struggle to access some parts of this website.

Some pages will be difficult or impossible to use for people with low vision or who use assistive technology, particularly screen reader users.

Interactive maps

Most of the interactive maps on this site:

  • are difficult or impossible to access using assistive technology, particularly for screen reader, keyboard and voice activation users
  • are hard to access for people with low vision or colour blindness, for example because they have poor contrast or use colour to convey critical information
  • do not currently have accessible text alternatives

Screen reader users will encounter the maps and some map controls, but we recommend you do not try to use the interactive maps.

If you have access problems, please contact us to request the information you need in an accessible format.

PDF documents

Most of the PDF documents on UK AIR are not fully accessible to users of assistive technology, particularly screen reader users. The PDF documents on this site:

  • have incorrect, inconsistent or missing markup or tagging
  • contain charts and images without descriptive alternative text or accessible text alternatives

Please contact us to request this information in an accessible format.

User input

Some pages on this site enable user input, for example forms and search features. Many of these pages have:

  • mislabelled elements, for example links that act like buttons, or fieldsets with no legend
  • error messages that do not explain what the problem is or how to fix it
  • user input components with unclear, confusing or insufficient labels
  • missing or unclear instructions
  • input fields with low-contrast placeholder text

If you have access problems, please contact us for support.

Other accessibility issues

Multiple pages on this site may have:

  • elements that are not accessible (or not fully accessible) to keyboard, screen reader or voice activation users
  • images, maps and charts with non-descriptive alternative text
  • links and buttons with unclear purpose or destination
  • text elements and non-text elements with low contrast against their background
  • incorrect or confusing heading structure
  • illogical, unexpected or unpredictable focus order
  • low-contrast or invisible focus indicators
  • insufficient visible or accessible labels
  • content that does not reflow correctly, for example some elements may overlap or obstruct others at reflow settings
  • use of symbols and characters that screen readers may not read correctly

Feedback and contact information

If you need information on this website in a different format like large print, easy read, audio recording or braille, contact ddu@defra.gov.uk.

We’ll consider your request and get back to you within 28 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 which aren’t mentioned in this statement, contact ddu@defra.gov.uk.

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).

If you live in Northern Ireland, complain to the Equalities Commission for Northern Ireland (ECNI).

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 and exemptions are listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

The non-compliances in this section were found by testing a sample of pages on UK AIR.

There may be similar accessibility issues on other pages on the website, along with the specific issues described. We’re working to find and fix these issues.

 

Maps and images with no accessible text alternative
  1. There are multiple decorative icons on the Home page with non-descriptive alternative text. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (A). We’re working to fix this issue by March 2025.

  2. Each news item under the News spotlight on the Home page starts with an arrow graphic. This graphic is a special character, resulting in a silent stop when read by screen reading software. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (A). We’re working to fix this issue by March 2025.

  3. On the Burn Better, Breathe Better: Reduce the negative impact your stove or open fire can have on your health page, there is an image containing a lot of text, with non-descriptive alternative text. Not all of the text in the image has an accessible alternative. The text in the image cannot be customised to meet the user's needs, which could be a problem for low vision and dyslexic users. This fails WCAG 2.2 success criteria 1.1.1 Non-text Content (A) and 1.4.5 Images of Text (AA). We’re working to fix this issue by March 2025.

  4. On the About Air Pollution page, the image of a map related to reporting the latest data for designation of UK non-agglomeration and agglomeration zones has non-descriptive alternative text and no text alternative. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (A). We’re working to fix this issue by March 2025.

  5. The page How Chlorofluorocarbons (CFCs) get to the Stratosphere when they are heavier than air contains a chart without an accessible text alternative. The image's alternative text does not describe the chart in appropriate detail. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (A). We’re working to fix this issue by March 2025.

  6. Multiple PDF files contain images and complex charts without appropriate descriptive text or accessible text alternatives. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content (A). We’re working to fix these issues by March 2026.

  7. The map on the Smoke Control Areas Map page has no text alternative. A lot of the information it contains is not available to users with limited vision, particularly screen reader users. Screen reader users will encounter an element with the role of 'application' but will not be able to access the map itself, which may be confusing. The map fails WCAG 2.2 success criteria 1.1.1 Non-text Content (A), 1.4.3 Contrast (Minimum) (AA) and 1.4.11 Non-text Contrast (AA). It also fails 1.4.1 Use of Color (A), because people who are colour blind may not be able to understand the meaning conveyed by the colour. We’re working to fix these issues by March 2026.

  8. There is a filter button on the List of Local Authorities with AQMAs page that contains a triangle symbol to indicate whether the filter options are expanded or collapsed. The arrow is a UNICODE character, so screen reading software announces it as 'filled up pointing triangle' or 'filled down pointing triangle', which may be confusing and time-consuming for screen reader users to hear. This fails WCAG 2.2 success criteria 1.1.1 Non-text Content (A) and 4.1.2 Name, Role, Value (A). We’re working to fix this issue by March 2026.

  9. There is an interactive map of the UK's geographical regions on the Home page, under the Latest measured air quality tab. The map uses a set of 10 low-contrast colours to show the air quality for each region, which may not be accessible to colourblind or low-vision users. This map fails WCAG 2.2 success criteria 1.1.1 Non-text Content (A), 1.3.1 Info and Relationships (A), 1.4.1 Use of Color (A) and 1.4.11 Non-text Contrast (AA). We’re creating an accessible alternative for this map, which will be available by April 2025.

 

Incorrect markup
  1. Multiple pages contain lists where the heading or introductory text are included in the list, so screen reader users will be given an incorrect count of list items. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re working to fix these issues by March 2025.

  2. Multiple pages have visual hierarchies that are not marked up properly with heading levels. Some pages skip heading levels or have multiple level 1 headings. Some pages use headings incorrectly for visual presentation purposes. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A), because screen reader users will not get an accurate understanding of the page structure or be able to accurately browse the page by its headings. We’re working to fix these issues by March 2025.

  3. Multiple pages contain radio buttons that are individually labelled but are not contained inside a fieldset. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A), because screen reader users will not get context for the radio buttons from a fieldset legend, and will not be able to focus on smaller and more manageable groups of buttons. We’re working to fix these issues by March 2025.

  4. Multiple pages do not have an accessible label on all their interface elements, such as lists, buttons, form fields and inputs, check boxes, and select components. Viewing the pages at different screen sizes, text labels may not be clearly associated with the components they are labelling. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (A) and 4.1.2 Name, Role, Value (A). We’re working to fix these issues by March 2025.

  5. There are some 'tags' under the Instructions heading on the Data Selector page. These tags are visually related, but this is not marked up for screen reader users. Also, the tags are grouped in-line instead of as a list, meaning screen reader software will announce them all as a single sentence. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re working to fix this issue by March 2025.

  6. There are multiple links on the Data Selector page that act like buttons, as they expand or collapse additional content. This may confuse users, particularly screen reader users, because this is not expected behaviour for a link. Also, the links do not convey their expanded or collapsed state to screen reader users. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (A) and 4.1.2 Name, Role, Value (A). We’re investigating how to fix this issue.

  7. Users can filter the List of Local Authorities with AQMAs by letter of the alphabet. These filters are marked up as links, even though they act like radio buttons. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re creating an accessible alternative for this information, which will be available by March 2026.

  8. On the Changes to Ratified Data page, there is a fieldset with no legend, so screen reader users may not be able to understand the context of the grouped content. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re working to fix this issue by March 2026.

  9. The Annual and Exceedance Statistics page is the start of a step-by-step process, but this is not made clear to screen reader users in the page title or page instructions. This fails WCAG 2.2 success criteria 2.4.2 Page Titled (A) and 2.4.6 Headings and Labels (AA). Also, each page in the process has a button at the end that suggests which step is next, but the labels are not descriptive for screen reader users. This fails 1.3.1 Info and Relationships (A). We’re working to fix this issue by March 2026.

  10. There is a visually numbered list of links on the Air Quality Library page, which is not marked up as an ordered list or with heading levels. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re working to fix this issue by March 2026.

  11. There is a list of reports on the Air Quality Library page, and each one has a link to view the full report. These links are visibly but not programmatically connected to the report they open (for example, through hidden descriptive text), so screen reader users may not be able to understand the purpose of the links. Also, each link opens a PDF document in a new tab, but this behaviour is not included in the links’ text. This fails WCAG 2.2 success criteria 1.3.1 Info and Relationships (A) and 2.4.4 Link Purpose (In Context) (A). We’re working to fix this issue by March 2026.

  12. A page containing a text description loads before the Smoke Control Areas Map does. Visibly, the map and its associated controls are not available until the user has activated the Accept button on this text page. But the map is accessible by screen reading software without activating this button, so screen reader users may not understand the map’s contents. This also means that 2 level 1 headings are available at the same time to screen reader users, which could be unexpected and disorienting. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A). We’re working to fix these issues by March 2026.

  13. Multiple PDFs have incorrect markup and tagging. Some have visual headings, heading structures and links that are not marked up correctly, or not marked up at all. Some contain tables that have irregular structures or have not been marked up correctly, while other PDFs are completely untagged, with no focusable elements. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships (A), because users of assistive technology may not be able to access or navigate the information in the files. We’re working to fix this issue by March 2026.

  14. The tag order is incorrect in multiple PDFs, so the information is not read out correctly to screen reader users, and the focus order will be incorrect when navigating the document via keyboard. This fails WCAG 2.2 success criterion 1.3.2 Meaningful Sequence (A). We’re working to fix these issues by March 2026.

 

Directional instructions
  1. On the Data Selector page, the introductory text contains directional instructions that rely on users having an awareness of where content is spatially located on the page This issue affects screen reader users who do not have access to visual information, and also anyone viewing the page on a narrow screen, because the content on the page responsively reorganises itself and will make the instructions incorrect. This fails WCAG 2.2 success criteria 1.3.3 Sensory Characteristics (A) and 3.3.2 Labels or Instructions (A). We’re working to fix this issue by March 2025.

 

Inaccessible use of colour and colour contrast
  1. On the Home page, there is an image of a map of the UK under the Air pollution forecast tab. This image uses a set of 10 low-contrast colours to show regional air quality, as defined by the legend below the map. There is no text alternative. This fails WCAG 2.2 success criteria 1.4.1 Use of Color (A) and 1.4.11 Non-text Contrast (AA), because people who are colourblind may not be able to understand the meaning conveyed by the colours. It also fails 1.3.1 Info and Relationships (A), because the information in the map is entirely visual and inaccessible to screen reader users, even though they will encounter the map legend. We’re creating an accessible alternative for this map, which will be available by April 2025.

  2. The different shades of blue in each section of the map on the About Air Pollution page have very low contrast. This fails WCAG 2.2 success criterion 1.4.1 Use of Color (A), because people who are colourblind may not be able to understand the meaning conveyed by the colours. We’re working to fix this issue by March 2025.

  3. Link text at the bottom of the Home page has very low contrast with the rest of the paragraph text, and has no other visible markers that it contains a link to Ricardo Energy & Environment. This fails WCAG 2.2 success criterion 1.4.1 Use of Color (A), because many users, and particularly people who are colourblind, may not be able to see that there is a link. We’re working to fix this issue by March 2025.

  4. On the Smoke Control Areas Map page, the menu items in the basemap selector rely on colour change alone to provide a visible focus indicator. This colour change does not have the required 3:1 contrast ratio against the background. This fails WCAG 2.2 success criterion 1.4.1 Use of Color (A), because low vision users navigating with a keyboard interface may not be able to see the focus indicator. We’re working to fix this issue by March 2026.

  5. The Pollution forecast page has a complex interactive map of the UK with a colour-coded overlay showing key information. The coloured overlay has low contrast and no text alternative. Even without the overlay, the contrast of the map itself is very low, and with the overlay active the contrast is even worse. At higher zoom levels, circular markers appear on the map, which also use low contrast colours and a small number to show individual air quality measurements. Screen reader users will have trouble accessing this map, and people with low vision may not be able to access or understand a lot of the map’s content. There is no text alternative. These issues fail WCAG 2.2 success criteria 1.3.1 Info and Relationships (A), 1.4.1 Use of Color (A), 1.4.3 Contrast (Minimum) (AA), and 1.4.11 Non-text Contrast (AA). We’re creating an accessible alternative for this map, which will be available by April 2025.

  6. The AQMAs interactive map has a complex interactive map of the UK with a colour-coded overlay showing key information. The coloured overlay has low contrast and no text alternative. Even without the overlay, the contrast of the map itself is very low, and with the overlay active the contrast is even worse. Some of the elements on the map are not included in the map legend and their purpose is not clear. Screen reader users will have trouble accessing this map, and people with low vision may not be able to access or understand a lot of the map’s content. There is no text alternative. These issues fail WCAG 2.2 success criteria 1.3.1 Info and Relationships (A), 1.4.1 Use of Color (A), 1.4.3 Contrast (Minimum) (AA), and 1.4.11 Non-text Contrast (AA). We’re creating an accessible alternative for this map, which will be available by September 2025.

  7. The Interactive monitoring networks map and Search for monitoring sites pages both have interactive embedded Google maps, showing the monitoring networks in the UK. These maps are complex and use many small, low-contrast features and text labels, which low vision users may not be able to see properly. No alternative format is provided. These issues fail WCAG 2.2 success criteria 1.3.1 Info and Relationships (A), 1.4.1 Use of Color (A), 1.4.3 Contrast (Minimum) (AA), and 1.4.11 Non-text Contrast (AA). We’re working to fix these issues by March 2026.

  8. Multiple PDFs contain colour-coded charts, and users would need to be able to see the colours and tell them apart to understand the charts. No alternative format is provided. This fails WCAG 2.2 success criterion 1.4.1 Use of Color (A). We’re working to fix this issue by March 2026.

  9. Multiple pages contain elements with low contrast against their background, including headings, titles, body text, links, buttons and tags. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (AA), because people, especially partially sighted people, will find it hard to read the text. We’re working to fix this issue by March 2025.

  10. Multiple pages contain input fields with placeholder text that has low contrast against its background, making it hard to read for everyone, but particularly partially sighted people. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (AA). We’re working to fix this issue by March 2025.

  11. The map on the Interactive monitoring networks map page uses different marker images to explain why some sites currently have no data. The only difference between the markers are the letters, which have low contrast against their background. The markers are also difficult to see against the map itself. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (AA). We’re working to fix these issues by March 2026.

  12. On the Daily Air Quality Index page, there is informational text shown in a light blue box. The text contains a link with low contrast against its background, and no underline or other sign that it is a link. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (AA). We’re working to fix this issue by March 2025.

  13. Multiple pages do not reflow correctly when using magnification or smaller screens. For example, at reflow settings, users need to scroll sideways to see some content, some content becomes unviewable, and some elements overlap or obstruct others. This fails WCAG 2.2 success criterion 1.4.10 Reflow (AA). We’re working to fix this issue by March 2026.
  14. Multiple pages have user interfaces, graphics and other non-text elements with low contrast against their background. This makes them hard to see for everyone, but particularly partially sighted people and keyboard users. This fails WCAG 2.2 success criterion 1.4.11 Non-text Contrast (AA). We’re working to fix this issue by March 2026.

 

Keyboard and focus
  1. On the Home page, there is an interactive vector graphic under the Latest measured air quality tab. This component is not accessible to keyboard, screen reader or voice activation users. There is no accessible alternative. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (A). We’re working to fix this issue by April 2025.

  2. Multiple pages need users to click on different points on the maps with a mouse to view information in a popup window. This is the primary purpose of the maps, but there is no way to access these popups by keyboard. Once the popups are open, they cannot be expanded or closed using a keyboard. This means the maps are unusable for keyboard, screen reader and voice activation users. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (A). We’re creating accessible alternatives for these maps, which will be available by March 2026.

  3. On the Smoke Control Areas Map page, the expandable button for the Legend is a custom control that is not accessible to keyboard-only users. Also, the button’s expanded or non-expanded state is not given to screen reader users. This fails WCAG 2.2 success criteria 2.1.1 Keyboard (A), 1.3.1 Info and Relationships (A) and 4.1.2 Name, Role, Value (A). We’re working to fix these issues by March 2026.

  4. On the Latest measured levels based on data provided by the Environment Agency page, users can open a dialog box using a keyboard, but they cannot close it with a keyboard. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (A), and 4.1.2 Name, Role, Value (A). We’re working to fix this issue by March 2026.

  5. On the Interactive monitoring networks map page, there is an inaccessible graphic of a question mark in the 'Filter by environment type' accordion. The graphic is not in the focus order and does not have an accessible name or visible label, meaning it is inaccessible by keyboard, screen reader and voice activation users. This fails WCAG 2.2 success criteria 2.1.1 Keyboard (A), 1.3.1 Info and Relationships (A) and 4.1.2 Name, Role, Value (A). We’re working to fix this issue by March 2026.

  6. On the Data Selector page, users can select a date range through a calendar interface. This interface is accessed using calendar icons that are not accessible by keyboard and do not have descriptive alternative text. This issue affects keyboard, screen reader, and voice activation users. This fails WCAG 2.2 success criterion 2.1.1 Keyboard (A) and 4.1.2 Name, Role, Value (A). It also fails 1.1.1 Non-text Content (A) and 1.3.1 Info and Relationships (A). Users are still able to enter dates manually. We’re working to fix this issue by March 2026.

  7. Multiple pages have illogical, unexpected, or unpredictable keyboard focus orders, sometimes making elements inaccessible when using a keyboard. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (A). We’re working to fix these issues by March 2026.

  8. On the Smoke Control Areas Map page, two elements in the legend are focusable at once, which may be confusing for keyboard users. These elements remain focusable even when the legend is collapsed. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (A). We’re working to fix these issues by March 2026.

  9. Multiple PDFs contain links that wrap across two lines, which have been split and tagged as links twice. This fails WCAG 2.2 success criterion 2.4.3 Focus Order (A), because it means multiple tab presses are needed to move through a single link. We’re working to fix these issues by March 2026.

  10. Multiple pages have radio buttons and other user interface elements that do not have a visible keyboard focus. This fails WCAG 2.2 success criterion 2.4.7 Focus Visible (AA), because keyboard users will not know where the cursor is on the page. We’re working to fix these issues by March 2026.

 

Missing page and document titles
  1. The Air Quality Information Bulletin – 9th September 2023 page has a non-descriptive page title, so it may be hard for screen reader users to know if they are on the correct page. This fails WCAG 2.2 success criterion 2.4.2 Page Titled (A). We’re working to fix this issue by March 2025.

  2. Multiple PDFs do not have document titles. This fails WCAG 2.2 success criterion 2.4.2 Page Titled (A), because it may be hard for screen reader users to know if they have the correct document. We’re working to fix these issues by March 2026.

 

Unclear link purpose
  1. On the Home page, the map under the Air pollution forecast tab is also a link, but its alternative text describes the image, not the link’s purpose or destination. All users, but in particular screen reader users, won't be able to work out where the link will go. This fails WCAG 2.2 success criteria 2.4.4 Link Purpose (In Context) (A) and 1.1.1 Non-text Content (A). We’re working to fix this issue by April 2025.

  2. On the Home page, under the Latest measured air quality tab, there is a group of map images that provides links to localised air quality information for each UK geographical region. The image group's alternative text contains a confusing variable substitution error, so it does not accurately describe any of the links’ purpose or destination. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context) (A) and 1.1.1 Non-text Content (A). We’re working to fix this issue by April 2025.

  3. On the Home page, there is a news item under the News spotlight heading whose title link is empty. Also, the keyboard focus becomes invisible when it focuses on the empty link, so keyboard users will not know where the cursor is on the page. This fails WCAG 2.2 success criteria 2.4.4 Link Purpose (In Context) (A) and 2.4.7 Focus Visible (AA). We’re working to fix this issue by March 2025.

  4. On the Data Selector page, when all selection criteria have been filled in, each one has links to edit and reset the field. The only way to know which links are for which selection criteria is the visual layout, which is inaccessible to screen reader users, particularly when browsing out of context. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context) (A). We’re working to fix this issue by March 2025.

  5. On the List of Local Authorities with AQMAs page, there is a table listing the Local Authorities with Air Quality Management Areas (AQMAs). In the second column, AQMA Name, some rows contain links where the link text is just a dash (-). This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context) (A). We’re working to fix this issue by March 2026.

  6. In the Agriculture Ammonia Emission Report PDF, there is an additional link at the end of the table of contents without any corresponding visual text. The link receives focus unexpectedly, with no description of its purpose or destination. Also, the URL that is announced to screen reader users for this link is incorrect. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context) (A) and 2.4.3 Focus Order (A). We’re working to fix this issue by March 2026.

  7. On the Data Selector page, under the Instructions heading, there are buttons labelled 'Save Selection', 'Update' and 'Reset'. For screen reader users browsing out of context, these labels are not descriptive of the buttons’ purpose. This fails WCAG 2.2 success criterion 2.4.6 Headings and Labels (AA). We’re working to fix this issue by March 2025.

  8. On the Data availability page, the user follows a multi-step process to choose what data they want to access. The button text to access each step in the process is not descriptive of the button’s purpose. The button text may also be confusing because the user has to press a button labelled Step 1 to go to step 2, a button labelled Step 2 to go to step 3, and so on. This fails WCAG 2.2 success criterion 2.4.6 Headings and Labels (AA). We’re working to fix this issue by March 2026.

  9. On the Pollution forecast page, there is an interactive map of the UK that shows location markers when the user zooms in. These markers all have the alternative text of 'Marker', so there is no way for screen reader users to tell them apart. This fails WCAG 2.2 success criterion 2.4.6 Headings and Labels (AA). We’re working to fix this issue by March 2025.

 

Insufficient labels and error messages
  1. Multiple pages contain user input components with insufficient labels. Either their visual labels do not match their accessible names, or the visual labels are in the form of placeholder messages that disappear when users start inputting text. This fails WCAG 2.2 success criteria 2.5.3 Label in Name (A) and 3.3.2 Labels or Instructions (A). We’re working to fix these issues by March 2026.

  2. Multiple pages give error messages that do not explain what the problem is or how to fix it. Also, the messages are shown in places that are confusing, unhelpful or could easily be overlooked, particularly for screen reader users. This fails WCAG 2.2 success criteria 3.3.1 Error Identification (A) and 3.3.3 Error Suggestion (AA). We’re working to fix these issues by March 2026.

  3. On the Mailing list page, the input fields in the form are required, and each label has an asterisk next to it. There are no instructions or labels to explain that the asterisks show required fields. There is also an asterisk next to the heading above the checkboxes, even though the checkboxes are optional. This fails WCAG 2.2 success criterion 3.3.2 Labels or Instructions (A) and 1.3.1 Info and Relationships (A). We’re working to fix these issues by March 2026.

  4. On the Home page, there is a select element that does not have a persistent visible label. This fails WCAG 2.2 success criterion 3.3.2 Labels or Instructions (A), because users may not know what input data is expected. We’re working to fix this issue by March 2025.

  5. On the Pollution forecast page, there are multiple components that control the map interface, but they do not have a label, a visible label or an accessible name. This affects all users, because the purpose of the components is not described, but it is particularly problematic for voice activation and screen reader users. This fails WCAG 2.2 success criteria 3.3.2 Labels or Instructions (A) and 4.1.2 Name, Role, Value (A). We’re creating an accessible alternative for this map, which will be available by April 2025.

  6. The interactive map on the Search for monitoring sites page has no visible labels. This fails WCAG 2.2 success criterion 3.3.2 Labels or Instructions (A), as sighted users will be unable to identify each section of the map correctly. We’re working to fix these issues by March 2026.

 

ARIA attributes used incorrectly
  1. In multiple places on the Home page, the ARIA role="tab" has been applied to containers, instead of the links inside. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (A), because screen reader users will encounter both a non-interactive container and an interactive link in context. We’re working to fix these issues by March 2025.

  2. On the Home page, there is a component under the Air pollution forecast tab that has been marked up as role="tab", within a role="tablist" container, despite only containing a single tab. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (A), because the component behaves like a disclosure or accordion, not a tab control, as there are no other tabs. We’re working to fix this issue by March 2025.

  3. In the site footer, there is an image of the Defra logo which has alternative text, but also has the contradictory aria-hidden="true" attribute. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (A). We’re working to fix this issue by March 2025.

  4. On the AQMAs interactive map page, when viewing the page on mobile, there is a button for expanding or collapsing the sidebar. But the attribute does not update when the sidebar is expanded, so it is always announced to screen reader users as being collapsed. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (A). We’re working to fix this issue by March 2026.

  5. On the Smoke Control Areas Map page, the basemap selector contains menu items with the aria-selected attribute applied. But this attribute is not valid on the role of 'menuitem', so this component may not be announced predictably to screen reader users. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value (A). We’re working to fix these issues by March 2026.

  6. Multiple pages have tabs that have not been allocated the role 'tab', though they are within an element with the role of 'tablist'. This fails WCAG 2.2 success criteria 4.1.2 Name, Role, Value (A) and 1.3.1 Info and Relationships (A). We’re working to fix these issues by March 2026.

  7. On the Pollution forecast page, after searching for and selecting a location, the selected location replaces the default location above the map. Screen reader users are not informed of this update to the page content. This fails WCAG 2.2 success criteria 4.1.3 Status Messages (AA). We’re working to fix this issue by March 2025.

  8. On the Data Selector page, there is an information box with the ARIA role="alert" attribute applied. For screen reader users, this will inappropriately cause an announcement starting with the word ‘alert’, interrupting any other announcement. This fails WCAG 2.2 success criteria 4.1.3 Status Messages (AA), because the content is only informational. We’re working to fix this issue by March 2025.

 

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

The accessibility regulations do not require us to fix videos published before 23 September 2020.

For example, we do not plan to fix the low-contrast text in the May 2018 Clean air strategy video, which fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (AA). Any new videos we publish will meet accessibility standards.

 

What we’re doing to improve accessibility

We are working to replace some of the major functions of this site with accessible alternatives by March 2026, particularly the interactive maps.

 

Preparation of this accessibility statement

This statement was prepared on 9 December 2024. It was last reviewed on 9 December 2024.

This website was last tested on 29 August 2024.

The test was carried out by the Digital Accessibility Centre. They tested the sample pages against the Web Content Accessibility Guidelines 2.2 using 2 different testing processes:

  • a manual technical audit, using automated tools
  • a dedicated team of user testers with differing disabilities, using a range of adaptive technologies

We consulted website owners and designers, the Digital Accessibility Centre, and page view data to decide on a sample of pages to test. We used this information to create a list of pages that are important for users of UK AIR, for example because they are:

  • commonly used
  • unique in format
  • representative of multiple pages on UK AIR