Designing and building Defra digital services

Accessibility statement for Defra digital standards

This accessibility statement applies to defra.github.io.

This website is run by Defra digital. 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:

  • you cannot skip to the main content when using a screen reader

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:

  • email [email address]
  • call [phone number]

We’ll consider your request and get back to you in 10 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: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].

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.

Find out how to contact us [add link to contact details page].

Technical information about this website’s accessibility

[Note: this form of wording is legally required, so do not change it.]

[Name of organisation] 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

[Note: say that the website is fully compliant if the website meets WCAG 2.1 AA standard in full. Say that it’s partially compliant if it meets most requirements of the WCAG 2.1 AA standard. If it does not meet most requirements of the WCAG 2.1 AA standard, say that it’s not compliant.

If your website is either partially compliant or not compliant WCAG 2.1 AA standard, you’ll need to explain why. This will be due to one or both of the following:

  • non-compliances - this means the content in question is in scope of the regulations, but there’s an accessibility problem with it
  • an exemption - this means the inaccessible content is out of scope of the regulations, or it’d be a disproportionate burden for you to make it accessible

There’s a legally required way of expressing the compliance status of your website, so do not change it. The 3 options are as follows:]

This website is fully compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The [insert one of the following: ‘non-compliances’, ‘exemptions’ or ‘non-compliances and exemptions’] are listed below.

[Note: delete the options that do not apply.]

Non-accessible content

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

GitHub?

What we’re doing to improve accessibility

[Note: publishing an accessibility roadmap is optional. It’s a good idea to publish one if you want to be specific about the order you’re planning to tackle accessibility issues, and there’s no space to do so in the accessibility statement itself.]

Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.

Preparation of this accessibility statement

[Note: the wording about when the statement was prepared is legally required, so do not change it.]

This statement was prepared on [date when it was first published]. It was last reviewed on [date when it was last reviewed].

This website was last tested on [date]. The test was carried out by [add name of organisation that carried out test, or indicate that you did your own testing].

We used this approach to deciding on a sample of pages to test [add link to explanation of how you decided which pages to test].