Accessible documents policy
This policy explains how accessible the documents the Youth Justice Board (YJB) publishes on GOV.UK are.
This policy covers PDFs, spreadsheets, presentations and other types of document. It does not cover content published on GOV.UK as HTML, the GOV.UK accessibility statement will cover that.
Using our documents
The YJB publishes documents in a range of formats, including:
- Microsoft Excel
- Microsoft Word
- ODT (OpenDocument Text)
- ODS (OpenDocument Spreadsheet)
- CSV (Comma-Separated Values)
We want as many people as possible to be able to use those documents. For example, when we produce a document we make sure to:
- provide an HTML option where possible
- use headings and other parts of the document properly, so screen readers can navigate the page structure
- make sure we include alt text alongside non-decorative images, so people who cannot see them understand what they’re there for
- avoid using tables, except when we’re presenting data
- write in plain English
How accessible our documents are
New documents we publish and documents you need to download or fill in to access one of the services we provide should be fully accessible.
However, we know that some of our older documents (published before 23 September 2018) are not accessible. For example, some of them:
- are not tagged up properly - for example, they do not contain proper headings
- contain images and charts without a textual description
- include complex tables
This mostly applies to our:
- corporate reports
- research and analysis reports
- statutory guidance
- forms
- statistics
These types of documents are exempt from the regulations, so we do not currently have any plans to make them accessible.
But if you need to access information in one of these document types, you can contact us and ask for an alternative format.
What to do if you cannot use one of our documents
If you need a document we’ve published in a different format, please email [email protected].
We’ll consider the request and get back to you in 15 working days.
Reporting accessibility problems with one of our documents
We’re always looking to improve the accessibility of our documents. If you find any problems not listed on this page or you think we’re not meeting accessibility requirements, contact us at [email protected].
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 the accessibility of our documents
The YJB is committed to making our documents accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The documents the YJB publishes are 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
Some of our documents have diagrams and/or tables. Some of these do not have a text alternative, so the information in them isn’t available to people using a screen reader. This does not meet WCAG 2.2 success criterion 1.1.1 (non-text content).
Some of our documents do not identify headings, lists or data tables correctly. This means users using screen readers may not be able to follow the structure of a document, which in turn may affect their ability to access and understand the information. This does not meet WCAG 2.2 success criterion 1.3.1 (info and relationships).
In some of our documents colour is used to differentiate types of information. This means users who cannot see will not be able understand the meaning the colour is supposed to convey. This doesn’t meet WCAG 2.2 success criterion 1.3.3 (sensory characteristics).
Some of our documents and pages contain images of text to convey information, rather than plain text. This means users either using a text-only browser or using assistive technology may not be able to understand the image of text. This doesn’t meet WCAG 2.2 success criterion 1.4.5 (images of text).
Some links in our documents do not contain context in the link text. This makes it hard for users using assistive technology to understand what the link is for, and where they would be directed to if clicked. This doesn’t meet the WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).
Some of our documents are not structured properly. This means they may not be accessible for users using screen readers or other assistive technology. This doesn’t meet WCAG 2.2 success criterion 4.1.2.
When we publish new documents we aim to make sure they are accessible. We fixed any accessibility issues with content in scope of the accessibility regulations by September 2020.
Content that’s not within the scope of the accessibility regulations
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.2 success criterion 4.1.2 (name, role value).
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.
Any new PDFs or Word documents we publish will meet accessibility standards.
How we tested our documents
We last tested a sample of our documents on 11 September 2020. The test was carried out internally by the YJB. We tested a sample of our documents and web pages across a range of accessibility criteria including:
- the use of headings and plain English
- the use of alternate text for images and tables
- compatibility with mobile devices
- correct HTML styling
- consistent navigation
- content works when zoomed in
- the colour contrast.
What we’re doing to improve accessibility
The YJB is:
- putting guidance and procedures in place to ensure that all new documents that we produce are accessible
- creating documents as HTML rather than PDF where possible
- raising awareness across the organisation on accessibility standards and encouraging the use of plain English in documents.
This page was prepared on 16 September 2020. It was last updated on 24 June 2024.