Are you OK with cookies?

We use small files called ‘cookies’ on on magistrates.judiciary.uk. Some are essential to make the site work, some help us to understand how we can improve your experience, and some are set by third parties. You can choose to turn off the non-essential cookies. Which cookies are you happy for us to use?

Accessibility statement

Using this website

The Judicial Office is responsible for the content of this website. The Ministry of Justice is responsible for the technical aspects.

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 the website using just a keyboard

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

What to do if you can’t access part of this website

If you need information on this website in a different format, you can contact us:

Judicial Office
11th floor, Thomas More Building
Royal Courts of Justice
Strand
London
WC2A 2LL

Email: website.enquiries@judiciary.uk

Reporting accessibility problems

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting the requirements of the accessibility regulations, contact website.enquiries@judiciary.uk giving details of the issue and any assistive technology you are using.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing 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

The Judicial Office is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliance issues listed below.

Non accessible content

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

Non compliance with the accessibility regulations

  • Users cannot access the cookie banner and preferences using voice controls. This fails WCAG 2.1 4.1.2 A (Name, Role, Value).
  • The screen reader focus gets trapped within the cookie banner. This fails WCAG 2.1 2.4.3 A (Focus Order).
  • The status of the checkbox for selecting cookie preferences isn’t communicated to screen reader users. This fails WCAG 2.1 4.1.2 A (Name, Role, Value).
  • The cookie banner is not displayed as a modal dialogue and the ‘Choose which cookies we use’ link suggests it will show expandable content. This fails WCAG 2.1 4.1.2 A (Name, Role, Value).
  • Form and button elements in the cookie banner are not labelled correctly and do not provide enough information to screen reader users. This fails WCAG 2.1 4.1.2 A (Name, Role, Value).
  • The text of some page components cannot be read when resized up to 200%. This fails WCAG 2.1 1.4.4 AA (Resize Text).

Disproportionate burden

Not applicable

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

PDFs and other documents

PDFs and other documents published before September 2018 are not accessible in a number of ways including missing text alternatives and missing document structure. 

Embedded videos

Embedded videos hosted on YouTube and other media players include non-accessible elements that are native to the video platform. For example, this means buttons to play videos are not descriptive enough for screen reader users as the context of the video is not clear. This fails WCAG 2.4.6 AA (Headings and Labels).

How we tested this website

We have completed accessibility checks using keyboard testing and the WAVE automated testing tool. The tests on the website were carried out by the Ministry of Justice.

What we’re doing to improve accessibility

We are working to fix the issues listed in this statement.

We will monitor the accessibility of this website on an ongoing basis and fix any accessibility issues reported to us.

This statement was prepared on 15 September 2020.