Accessibility statement

This accessibility statement applies to employer accounts with the Apprenticeship Service.

This website is run by the Department for Education. 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 that some parts of this website are not fully accessible. For example:

  • select page regions are not identified with ARIA landmarks
  • some elements are not using supported ARIA attributes
  • there is insufficient contrast between the text and the background in some elements
  • different page links with identical text are always not distinguishable by their accessible label
  • users navigating with Dragon Naturally Speaking cannot interact with the ‘Help’ content
  • some data tables are not marked up correctly with table headers
  • navigational items are skipped when navigating with iOS VoiceOver
  • related links are not grouped using a nav element
  • incorrect autocomplete attributes are used in some data fields
  • not all drop-down menus are not announced to screen reader users
  • some error messages are announced repeatedly for screen reader users
  • headings are not appropriately structured or marked up correctly across the site
  • the tab order is not always logical when using mobile screen readers
  • html validation errors are present on some pages

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 5 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, contact:

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

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

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

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

Technical information about this website’s accessibility

The Department for Education 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 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

  1. An empty table header is present within data tables. Screen readers may apply heuristics to decide whether a table is a layout table or a data table and might not announce the content correctly. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
  2. Multiple instances of generic link text such as ‘Details’ are present, which do not sufficiently inform screen reader users where they will be navigated to upon interaction with the links. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).
  3. When navigating the site with iOS VoiceOver screen reader enabled, menu navigation items are skipped after interacting with the ‘More’ menu item. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
  4. While using screen readers JAWS, NVDA, Android Talkback and iOS Voiceover, dropdown menu items are not announced as expandable. Users of screen readers would not know that these navigational items can be expanded and may miss out on vital information. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value.
  5. A correctly formed heading structure is not present to facilitate navigation across the site, with skipped heading levels present. This fails WCAG 2.2 success criterion 2.4.1 Bypass Blocks.
  6. Headings are not marked up appropriately which may cause screen readers to announce them incorrectly. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships.
  7. Links with identical text are not distinguished by their accessible labels. This could cause confusion for screen reader users. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context).
  8. The Settings dropdown within the navigational menu is not announced correctly. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value.

We will aim to fix the above issues by December 2025.

  1. ARIA landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
  2. Some elements do not use supported by ARIA attributes, which may interfere with the accessibility of the webpage. This can mainly be seen where radio buttons are present. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

The ‘Beta’ banner, breadcrumbs and ‘Back’ link are not contained within an ARIA landmark. Users who rely on ARIA landmarks for navigation may unintentionally miss or skip the content not correctly contained within ARIA landmarks. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.

  1. The breadcrumb links on ‘Manage Transfers’ and ‘My Transfer pledges’ are not contained within a <nav> element. Related links that are visually grouped, but not contained within a <nav> do not support users of assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
  2. The autocomplete attribute present on the location form input on the ‘Add the locations you'd like to fund’ webpage is not appropriate. The autocomplete attribute ‘new-password’ does not align with the form field's purpose. This may result in users who use autocomplete inputting incorrect data. This fails WCAG 2.2 success criterion 1.3.5 - Identify Input Purpose.
  3. While using screen readers JAWS, NVDA, Android Talkback and iOS Voiceover, presented error messages are announced multiple times. This fails WCAG 2.2 success criterion 4.1.3 - Status Messages.
  4. When using a mobile screen reader, the focus order of the page is not always logical. This includes elements being announced when they are not displayed. This fails WCAG 2.2 success criterion 2.4.3 Focus Order.
  5. Some uses of ARIA are not appropriate and may result in some content being announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value.

We are working alongside other government departments and agencies to fix the above issues.

Disproportionate burden

We are unable to fix any issues that relate to the ‘Help’ pop-up as it managed by a third-party, so it is exempt from meeting the accessibility regulations. This is known as disproportionate burden within the meaning of the accessibility regulations.

We will make another assessment when the supplier contract is up for renewal.

What we’re doing to improve accessibility

We will do ongoing accessibility testing of all areas of the employer account to meet WCAG2.2. We are fixing issues 1-8 listed above as a priority.

Preparation of this accessibility statement

This statement was prepared on 20/09/2024. It was last reviewed on 27/01/2025.

This website was last tested on 19/09/2024. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define a representative selection of pages and test approach.