Accessibility statement for Tell Us Once

This service is part of the wider GOV.UK website. There's a separate accessibility statement for the main GOV.UK website.

This statement only applies to the Tell Us Once service, available at https://tell-us-someone-died.dwp.gov.uk.

Using this service

This service is run by the Department for Work and Pensions (DWP). We want as many people as possible to be able to use this service. 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
• get from the start of the service to the end using just a keyboard
• get from the start of the service to the end using speech recognition software
• listen to the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the text in the service 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:

• the warning about the session time expiring does not work as expected
• Welsh is not always translated
• landmarks (that help identify the structure of a web page in code) are not always correctly identified
• some links may be difficult for speech-recognition users to access
• some links are missing visual text
• some links point to different content than expected from the text in the link
• it is not clear where some links go based on the link text or closely related content
• some links are missing focus styles so are difficult to see with a keyboard
• some buttons do not perform the intended action when used with a keyboard
• heading hierarchy is not always correct and may lead to incorrect reading of content
• headings are not always correctly identified for screen readers
• some fields are not labelled
• some labels do not clearly describe what is being asked for
• it is not always clear when a question is required or optional
• the relationship between fields is not always indicated
• error messages and format information are not always announced by screen readers when fields are focused
• sometimes questions ask for information which has already been provided
• not all information entered is available to be reviewed before being submitted
• some content is cut off when the page is zoomed in or viewed on smaller devices
• the cookie banner obscures focus state in the footer
• it’s not always clear how to recover from error messages
• errors are not always correctly identified
• the purpose of fields collecting personal information cannot be determined from the code
• changes to the page contents are not communicated to screen reader users

Feedback and contact information

If you have difficulty using this service you can contact us:

Email: tellusonce.communications@dwp.gov.uk

Telephone: 0800 085 7308

Relay UK(if you cannot hear or speak on the phone): 18001 then 0800 085 7308 British Sign Language (BSL) Video Relay Service if you’re on a computer - find out how to use the service on mobile or tablet

Monday to Friday 8:00am to 6:00pm (except public holidays)

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page, or think we’re not meeting accessibility requirements, you can report an accessibility problem.

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) if you live in England, Scotland or Wales
• Equality Commission for Northern Ireland (ECNI) if you live in Northern Ireland

Technical information about this website’s accessibility

The Department for Work and Pensions 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 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

• The functionality to extend the time of the session is not always presented and, when it is, does not always work. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value) and 2.2.1 (Timing Adjustable).
• Several languages are shown on a page but they are not correctly identified in code.. This fails WCAG 2.2 success criterion 3.1.2 (Language of Parts).
• Some landmarks (that help identify the structure of a web page in code) are missing correct roles or accessible names. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
• Some links do not contain the visual text in the accessible name. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name).
• Some links are missing an accessible name. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
• Some links point to different content than expected from the text in the link. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).
• The purpose of some links is not clear from their immediate context. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).
• Some links are missing visible focus styles. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
• Some buttons action unrelated buttons when used with a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard), 2.4.4 (Link Purpose (In Context)) and 3.3.4 (Error Prevention (Legal, Financial, Data)).
• Heading hierarchy is not always correct and may lead to incorrect reading of content. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Content is visually and contextually presented as headings but is missing the semantic information. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Some fields are not labelled. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value).
• Some labels do not clearly describe what is being asked for. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels).
• It is not always clear when a question is required or optional. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
• The relationship between fields is not always indicated. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Error messages and format instructions are visually associated with fields but not associated programmatically in the code. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Sometimes questions ask for information which has already been provided. This fails WCAG 2.2 success criterion 3.3.7 (Redundant Entry).
• Not all information entered is available to be reviewed before being submitted. This fails WCAG 2.2 success criterion 3.3.4 (Error Prevention (Legal, Financial, Data)).
• Some content is cut off when the page is zoomed in or viewed on smaller devices. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
• The cookie banner obscures focus state in the footer. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured (Minimum)).
• It’s not always clear how to recover from error messages. This fails WCAG 2.2 success criterion 3.3.3 (Error Suggestion).
• Errors are not always correctly associated with the field they relate to. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
• The purpose of fields collecting personal information cannot be determined from the code. This fails WCAG 2.2 success criterion 1.3.5 (Identify Input Purpose).
• Dynamic changes to page content are not communicated and require the user to move focus to discover. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).

We plan to fix these issues by 6 April 2027.

What we’re doing to improve accessibility

We’re aiming to be fully compliant with the WCAG 2.2 AA standard by 6 April 2027. We will continue to iterate the design of the service and continue to test the service against the WCAG 2.2 AA standard.

Preparation of this accessibility statement

This statement was prepared on 29 October 2024. It was last reviewed on 25 February 2026.

This service was last tested in January 2026 against the WCAG 2.2 AA standard. The test was carried out by the Department for Work and Pensions. The service was tested using both automated and manual testing.