Each page must have a unique title that indicates its topic or purpose. This ensures that people with cognitive disabilities can quickly orientate themselves within the service and identify the purpose of the page without interpreting its entire contents.
Accessibility Requirements for 2.4.2 Page title (A)
- Each page has a title that is unique within the service;
- Each page has a title that indicates its topic or purpose.
Common mistakes for 2.4.2 Page title (A)
- The page title is not unique within the service;
- The page title does not indicate its topic or purpose;
- The title does not indicate the page is part of a service on Gov.UK;
- The page title does not change because the service is a Single Page Application (SPA).
Techniques 2.4.2 Page title (A)
Your site doesn’t include support for the Accordion Item block. You can try installing the block, convert it to a Custom HTML block, or remove it entirely.
Common Failures 2.4.2 Page title (A)
The following are common mistakes that are considered failures of Success Criterion 2.4.2 by the WCAG Working Group.
FAQs for 2.4.2 Page title(A)
Few tips for Page title
A useful format for writing page titles is: ‘Page name – Page description – Website name’
If pages are part of a process, such as a checkout, use the title to tell the user what stage they’re at
Don’t forget dynamic pages such as search results (‘Search Results for XXX’) and 404 errors
In many cases, it makes sense to repeat the page title or a variation of it as the top heading on your page.
Type your page titles into a spreadsheet and review them. If they make sense out of context, they will work on your website.
Use these page titles in your sitemap to make it more accessible.
How to ensure Page title is in place?
The page title should be placed in the
<title> element within the
<head> of the document.
Replace any filler or placeholder text with a page title that identifies the subject of the page, makes sense out of context (for example, in a search result list), and is concise.