- Success Criterion 2.4.2
- Conformance level A
Embedded Document or Frame Used as a Page With No Title
2.4.2 — Page Titled
Scenario
Setting
A public library's catalog search
What’s wrong
Iframes aside: framesets/embedded documents relied on as pages lacking titles.
Example
<title></title>Why it matters
Screen-reader users who hear the title first, and anyone managing many tabs.
How to test
Check any frameset or embedded document relied on as a standalone page: if it has no title element, it fails.
How to fix
Every page/view must have a unique, descriptive title identifying its content, updated on in-app navigation.
<title>Checkout — Step 2 of 3: Shipping — Acme Store</title>A descriptive, unique title lets users identify and switch between tabs or windows without guessing.
Outcome
On a public library's catalog search, this barrier is gone for screen-reader users who hear the title first — they can complete the task without hitting this wall.
Who is affected
Screen-reader users who hear the title first, and anyone managing many tabs.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Page Title That Doesn’t Say What the Page Actually Is
- Page Published With a Missing or Empty Title Tag
- Identical Page Title Repeated Across an Entire Website
- Single-Page App Title That Never Updates Between Views
- Page Title That’s Just the Brand Name, No Topic
- Page Title That Doesn’t Reflect the Current Step or State