Accessibility statement for AHDB

This accessibility statement applies to the AHDB website ahdb.org.uk 

Our aim is to be compliant with the Web Content Accessibility Guidelines version 2.2 AA standards and maintain these standards with continuous review of the site content and structure. 

This website is run by AHDB. 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 400% without the text spilling off the screen
  • Navigate most of the website using a keyboard or speech recognition software
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We 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 image link elements use an old styling that has poor contrast 
  • There are pages that have poor accessibility features, e.g. not all areas can be navigated to using the keyboard and focus is not always visible
  • Some older embedded videos do not have captions or titles
  • Some pages and documents attached are not written in plain English
  • Some tables do not indicate if they are a layout or a data table
  • Some information in tables cannot be reached with a keyboard
  • Some tables do not have row or column headings
  • Some charts and graphs are not fully accessible as they rely on colour, have poor colour contrast or lack alternative text descriptions
  • Some documents have poor colour contrast
  • Many documents are in PDF format and are not accessible

Known issues last updated: January 2026

Feedback and contact information

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

In your message, please include: 

  • ‘Accessibility’ in the subject
  • The web address (URL) of the content 
  • Your email address and name 

Reporting accessibility problems with this website

If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact: info@ahdb.org.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).

Technical information about this website’s accessibility

AHDB 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

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

Non-accessible content

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

Non-compliance with the accessibility regulations

  1. The focus is not fully visible when at 200% or above on the main menu options. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible) success criterion. We plan to fix this issue by August 2026.
  2. On 400% zoom some of the footer links are not legible when they have focus. This fails WCAG 2.2 success criterion 1.4.10 (Reflow). We plan to fix this by December 2026.
  3. Not all headings are identifiable as they use CSS heading styles rather than HTML headings. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this issue by June 2027.
  4. There are elements that are not owned by the correct parent role. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this issue by December 2026.
  5. Some tables do not have table row or column headers. This means assistive technologies will not read the tables correctly. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this issue by June 2027.
  6. There are some tables that do not indicate if they are a layout or a data table. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this issue by June 2027.
  7. Not all links are underlined. This fails WCAG 2.2 success criterion 1.4.1 (Use of Colour). We plan to fix this issue by December 2027.
  8. Not all areas of text or buttons have sufficient contrast with the background colour. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)). We plan to fix this issue by December 2026.
  9. Not all data tables have their data cells associated with the relevant header cell. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix this issue by June 2027.
  10. Not all links have an accessible name. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content). We plan to fix this issue by December 2026.
  11. Not all documents have a title. This fails WCAG 2.2 success criterion 2.4.2 (page titled). We plan to fix this issue by June 2027.
  12. An element which is hidden contains focusable content. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to fix this issue by June 2027.
  13. iframe and frame elements do not always have a title element. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to fix this issue by December 2026.
  14. Some graphs and charts use colour as the only way to convey meaning. This fails WCAG 2.2 success criterion 1.4.1 (Use of Colour). We plan to fix this issue by June 2027.
  15. Some pages use images of text instead of text. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text). We plan to fix this issue by June 2027.
  16. Some headings don’t accurately describe the content underneath. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels). We plan to fix this issue by June 2027.
  17. Some older embedded videos do not have captions (prerecorded). This fails WCAG 2.2 success criterion 1.2.2 (Captions Prerecorded). We plan to fix this issue by June 2027.
  18. Some older embedded videos do not have titles. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled)We plan to fix this issue by June 2027.
  19. Some alt text contains placeholders like ‘picture’ or ‘spacer’. This fails WCAG 2.2 success criteria 1.1.1 (non-text Content) and 1.2.1 (Audio-only and Video-only (Prerecorded)). We plan to fix this issue by December 2026.
  20. Some areas of the website cannot be accessed using the keyboard. This fails WCAG 2.2 success criterion 2.1.1 (keyboard). We plan to fix this by June 2027.
  21. Visible focus is not always seen on some pages. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible). We plan to fix this issue by June 2027.
  22. Webpages should provide a way to skip to the main content of the page, none of our webpages allow users to quickly skip to content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to fix this issue by December 2026. 
  23. Some of our pages have adjacent links (picture and text) that point to the same destination and these should be combined into one link only. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content). We plan to fix this issue by August 2026.

Many documents are in non-HTML formats, for example PDFs. They are not accessible in a number of ways, including missing text alternatives, missing document structure, missing meta data or inaccessible content formatting. We plan to fix this issue by December 2026. 

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

PDFs and other documents

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

What we are doing to improve accessibility

We are working to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard. We have provided dates for when we plan to fix the issues in our 'Non-compliance with accessibility regulations' section.

Preparation of this accessibility statement

This statement was prepared in November 2020. It was last reviewed on 29 January 2026.

This website was last tested in October 2025 against the WCAG 2.2 AA standard.

The test was carried out by AHDB using Sort Site Professional. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.

To request a copy of the full accessibility report, email: info@ahdb.org.uk

Find out what we're doing to make our website accessible

×