Accessibility
We want the DLH.io website to be accessible and usable for as many people as possible.
We try to make our site more accessible by using:
- easier to read colours
- larger fonts
- plain English
- keyboard only navigation
- responsive designs to support page reflow into a single column when you resize your page
- designs which allow the ability to listen to the majority of the website with a screen reader
Feedback and contact information
If you cannot access any part of this site or want to report an accessibility problem, please contact us.
Enforcement procedure
The Equality and Human Rights Commission enforces the accessibility regulations (the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018).
If you're not happy with how we respond to your feedback, contact the Equality Advisory and Support Service. They are an independent advice service. They will advise you on what to do next.
Compliance status
DLH.io is committed to making its website accessible.
The website is partially compliant with the Web Content Accessibility Guidelines version 2.2 (WCAG) A and AA success criteria.
Not compliant with the accessibility regulations
Below is our content which is currently not compliant with the accessibility regulations:
- You cannot modify the line height or spacing of text. This fails WCAG 2.2 success criterion.
- Most older PDF documents are not fully accessible to screen reader software. This fails WCAG 4.1.2 success criterion.
- Some of our PDF forms are difficult to navigate using just a keyboard. This fails WCAG 2.2 success criterion.
- Audio descriptive, transcript and signed versions for some our video content are currently not provided. This fails WCAG 2.2 success criterion 1.2.3 (audio description or media alternative pre-recorded).
The DLH.io Platform and Application
The DLH.io platform and application are mainly compliant with accessibility regulations with the following highlighted as considerations for future accessibility modification:
- Audio CAPTCHA cannot be completed by any user with a hearing impairment as the sound is distorted to avoid bots. This fails WCAG 1.3, 2.1.1 and 4.1 success criterion.
- Optional fields not announced by Screen Reader. Form instructions are not accessible to assistive technology users. We use ‘optional’ which is fine for sighted users but not read by screen readers. This fails WCAG 3.3.2 success criterion.
- Mobile devices. N/A.
We plan to have various issues fixed by September 2026.
Disproportionate burden
There is currently no content on our website which we are claiming.
If this changes, this section will be updated.
Not within the scope of regulations
Older PDFs do not meet accessibility standards. For example, they may not be structured to be accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.
We plan to either remove these or replace them with accessible HTML pages in due course.
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 documents we publish will aim to meet accessibility standards.
Preparation of this accessibility statement
This statement was first prepared on 08/07/2025 and last reviewed on 10/06/2025 following an evaluation on the DLH.io website.
The method used to prepare this statement was a self-assessment by DLH.io. The self-assessment followed the WCAG Evaluation Methodology. Ongoing internal reviews are conducted on content published on this website and design system components used to construct the site.