Operable · Level A · Introduced in WCAG 2.0
WCAG 2.4.2: Page Titled
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Each page needs a title describing its topic or purpose. Titles help users distinguish browser tabs, history entries and screen-reader announcements when moving between pages.
A practical example
Three application steps all use “Portal.” Give them distinct titles such as “Contact details – Permit application” and “Review – Permit application,” updating the title when the route changes.
How to check it
- Inspect the document title on each representative route and process step.
- Compare the title with the visible page purpose and with titles on similar pages.
- Navigate client-side and directly reload the destination to verify both paths produce the correct title.
What can be missed
The visible H1 does not automatically set the browser title. Unique wording is useful, but a unique identifier alone may still fail to describe the page's purpose.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.