Accessibility statement for Teaching Vacancies

Teaching Vacancies is run by the Department for Education. We want as many people as possible to be able to use the service. For example, that means users 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 service using just a keyboard
  • navigate most of the service using speech recognition software
  • listen to most of the content on Teaching Vacancies using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the text on the service as simple as possible to understand.

How accessible Teaching Vacancies is

Teaching Vacancies is currently designated as 'partially accessible' according to the Web Content Accessibility Guidelines version (WCAG) 2.1 AA standard. All significant issues with accessibility are detailed in the Non-accessible content section, below.

Reporting accessibility problems with Teaching Vacancies

We’re always looking to improve the accessibility of this service. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, please email with 'Accessibility issues' in the subject line of the email.

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 Teaching Vacancies' accessibility

The Department for Education is committed to making its digital services accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is at present partially compliant with the WCAG 2.1 AA standard, due to those non-compliance issues listed below that are marked with (A) or (AA).

Non-accessible content

A number of issues related to the accessibility of Teaching Vacancies were raised in an accessibility audit conducted in May 2019. Most of these have been corrected but there are still a number of issues the Teaching Vacancies team is working to resolve. When these issues have been resolved we will update this statement and the compliance status of Teaching Vacancies.

Non-compliance with the accessibility regulations

The following accessibility issues have been identified and are grouped here according to which principle of accessibility criteria they fall under in the WCAG 2.1 guidelines.


Principle: Information and user interface components must be presentable to users in ways they can perceive.

Issue: Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader.
Criterion failed : 1.1.1 Text Alternatives: Non-text content (AA)
Will be resolved: October/November 2019

Issue: The colour contrast ratio between text and its background colour on certain pages makes text difficult for visually impaired users to read. Increasing the text size will resolve this issue.
Criterion failed: 1.4.3 Distinguishable: Contrast (Minimum) (AA)
Will be resolved: October/November 2019


Principle: User interface components and navigation must be operable.

Issue: The 'skip to content' link that allows users of assistive technology to skip navigation links and go straight to the main content isn't working in Internet Explorer.
Criterion failed: 2.4.1 Navigable: Bypass Blocks (A)
Will be resolved: October/November 2019

Issue: Some hyperlinks on the service need more useful descriptions for users of screen readers, who require context for each link.
Criterion failed: 2.4.9 Navigable: Link Purpose (Link Only) (AAA)
Will be resolved: October/November 2019

Issue: Header text on the page confirming to a user that they've signed up for a job alert skips a heading level (for example, jumping from an h2 level to an h4 level), which can cause confusion for users navigating pages with a screen reader.
Criterion failed: 2.4.10 Navigable: Section headings (AAA)
Will be resolved: October/November 2019


Principle: Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

Issue: Users of screen readers aren't reliably notified when a page is loading or when jobs have been sorted by date. This leads to the focus remaining stationary.
Criterion failed: 4.1.3 Compatible: Status messages (AA)
Will be resolved: October/November 2019

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

The following accessibility issues have been identified but do not fall within the scope of the WCAG 2.1 guidelines for the reasons stated.

Issue: The colour used to indicate when an element such as a radio button has received focus does not meet the expected ratio. This is a GDS Design System issue, however, so is not within our scope to correct. Note that a subtle movement effect also helps convey the focus state of a button, for example, so colour contrast is not the only tactic we use for improving distinguishability.
Criterion failed: 1.4.11 Distinguishable: Non-text contrast

How we tested this website

This website was last tested on 28 May 2019. The test was carried out by the Digital Accessibility Centre (DAC).

DAC tested various combinations of the following for both desktop and mobile/tablet users:

  • assistive technologies (eg Jaws 16, NVDA, VoiceOver, Dragon Voice Activation, Keyboard, System inverted colours, Screen Magnification, Colour blind checks, Resizing content)
  • browser environments (IE11, Firefox, Safari, Chrome)
  • accessibility user groups (Blind, Deaf, Mobility, Colour blind, Dyslexia, Low Vision, Aspergers, Cognitive Impaired/Panic/Anxiety)

DAC tested:

This statement was prepared on 12 September 2019. It was last updated on 12 September 2019.