Accessibility issues
Common accessibility issues
- Last reviewed
- 14 September 2026
- Owner
- DesignOps
**Level 1 — Find your topic
Error messages | Headings | Images | Links | Dynamic content | Colour
Level 2 — Understand the problem
Short explanation of why it matters.
Level 3 — Fix it
Clear recommendation + example + authoritative further guidance.**
Many DfE products and websites contain similar accessibility issues. You can prevent many of these issues by following accessible design and development practices.
This guidance covers some of the issues we find most often. Use it to understand the problem, how it can affect users and what you can do to prevent or fix it.
Error messages
Create error messages that clearly explain what has gone wrong and how the user can fix it.
[Follow GOV.UK guidance on error messages]
Non-descriptive error messages
Generic or unclear error messages can make it difficult for users to understand what went wrong and what they need to do.
Do
Use a clear message that describes the problem and tells the user how to fix it.
Don't
Use a generic or ambiguous error message that does not explain what went wrong.
Errors from a server or database
Server or database errors can expose technical information and may be difficult for users to understand.
Do
Catch technical errors and provide a clear, user-friendly message.
Don't
Show database-generated or technical error messages to users.
Error messages not linked to the input
Linking an error message to the relevant input helps users find and correct errors. This is particularly important for people using screen readers.
Do
Link the error message to the input that contains the error.
Don't
Use plain text that does not identify the input containing the error.
Headings
Use headings to create a logical structure that helps users understand and navigate your content.
[Follow GOV.UK guidance on headings]
Use a logical heading structure
Use headings in a logical order to show the hierarchy of your content.
Do
Use headings that clearly show the structure of the page.
Don't
Skip heading levels in a way that makes the structure difficult to understand.
Use semantic headings
Use the correct HTML markup for headings so screen reader users can navigate the page.
DfE digital services should generally use H1, H2 and H3 headings. If your content needs more levels, consider whether the content or page structure should be redesigned.
Do
Use semantic HTML heading elements.
Don't
Style paragraphs or other elements to look like headings.
Images, charts and alt text
Make sure people who cannot see your images or charts can understand the information they contain.
[Follow GOV.UK guidance on accessible images]
Alternative text
Alternative text should describe the purpose or information conveyed by an image.
Do
Write alternative text that accurately describes the image when the image provides useful information.
Don't
Use filenames or misleading descriptions as alternative text.
Charts and data
Make sure information in charts can be understood without relying on colour alone.
Do
Use labels and other ways of communicating the information in a chart.
Don't
Use colour alone to distinguish data or communicate meaning.
Descriptive links
Use clear and descriptive link text so users can understand where a link will take them.
[Follow GOV.UK guidance on links]
Repetitive links
Where the same type of action appears repeatedly, make sure users can understand what each link relates to.
You can use visually hidden text where additional context is needed, such as repeated edit links.
Non-descriptive links
Do
Use concise link text that describes the destination or action.
Don't
Use generic link text or link an unnecessarily long sentence.
Changes to content
Make sure changes to content made by JavaScript are communicated to people using assistive technologies.
Dynamic content changes
Use appropriate ARIA techniques where they are needed to communicate changes to screen reader users.
Incorrect use of ARIA can make an experience worse. If you need advice on implementing ARIA live regions, contact DesignOps.
[Find out more about ARIA live regions]
Colour
Make sure colour does not prevent people from accessing or understanding your content.
DfE digital services should follow GOV.UK guidance for colour.
Text contrast
Use sufficient contrast between text and its background.
Normal text should have a contrast ratio of at least 4.5:1 and large text should have a ratio of at least 3:1.
[Check your colour contrast]
Non-text contrast
Important non-text elements, such as controls, should have sufficient contrast against the background.
The minimum contrast ratio for non-text elements is 3:1.
Focus states
Use the default GOV.UK Design System focus styling.
Changing the colour or style of focus states can make them harder to recognise and can cause inconsistency across DfE services.
Other accessibility guidance
For accessibility guidance that is not covered here, use the relevant GOV.UK and DfE Design System guidance.
If you need specialist advice, contact DesignOps.