Powered by
Names, roles & states
Two or More Frames Share the Same Title
When embedded frames have the same title, screen reader users can't tell them apart, so they open the wrong one or skip what they need.
frame-title-uniqueWCAG 2.0Introduced in WCAG 2.0.Level AA — the minimum. Missing it blocks people outright.
- Status
- SeriousSerious — Significant friction, or information that is lost.CurrentScanners run this rule today.
- Owner
- DevContentTest
- Audit
- Automated+ManualA scanner finds it; a person confirms the fix.
Why it matters
A frame (an iframe) is a page placed inside another page, such as a video, map, form or advert. Its title is the name a screen reader reads out.
Screen reader users can list every frame on the page and jump to one. If two frames are both called "Embedded content", the list is useless. They must enter each frame to guess what it holds.
Who it affects
| Who | What they experience | Impact |
|---|---|---|
| Screen reader users | They hear the same frame name twice and can't tell which is the video and which is the map. | High impact |
| Low-vision users (magnification) | Affected only if they also use a screen reader, as many do. | Partial impact |
| Cognitive and neurodivergent users | Hearing the same name for different content is confusing and slows them down. | Partial impact |
| Voice control users | Saying the frame's name may pick the wrong one, or ask them to choose between identical options. | Partial impact |
Business & product impact
| Area | Why | Impact |
|---|---|---|
| Legal | It relates to WCAG 4.1.2 at Level A, the minimum. Complaints under Australia's Disability Discrimination Act and EN 301 549 point to WCAG. | High impact |
| Conversion | If the payment or booking frame can't be found, people may give up. | Moderate impact |
| SEO | Search engines don't reward unique frame titles — don't sell it as an SEO fix. | Low impact |
| Brand trust | Generic, repeated labels signal that nobody tested with a screen reader. | Low impact |
| Cost to fix | A small text change. Make the title a required setting in your embed component. | High impact |
Fixing it in code
A video and a map on one page
Don't
<iframe src="https://video.example/123" title="Embedded content"></iframe>
<iframe src="https://maps.example/store" title="Embedded content"></iframe>A screen reader says: “Embedded content, frame … Embedded content, frame”
Do
<iframe src="https://video.example/123" title="Video: How to return an item"></iframe>
<iframe src="https://maps.example/store" title="Map: Our Sydney store"></iframe>A screen reader says: “Video: How to return an item, frame … Map: Our Sydney store, frame”
Each title now says what is inside, so people can pick the right one.
Fixing it in design and content
Writing frame titles
Don't
Every embed gets the default title from the tool, like "YouTube video player".
A screen reader says: “YouTube video player, frame … YouTube video player, frame”
Do
Each title names the content: "Video: Setting up your account", "Video: Changing your password".
A screen reader says: “Video: Setting up your account, frame … Video: Changing your password, frame”
Titles that describe the content are unique and useful.
Designer's handoff note
When you place an embed in a design, write its title next to it. Say what it is and what it shows.
Quick test
Tool
NVDA (opens in a new tab) (free on Windows)
Checklist
- Pass
- Each frame has a different name that says what is inside.
- Fail
- Two frames have the same name, or names like "frame" or "embedded content".
Check these at the same time
- The page has no title
document-title
What a green scan still misses
A scanner can see that two titles match. It can't tell if a unique title actually describes what's in the frame.
Reference
- Rule ID
frame-title-unique- Raised by
- axe-core: “Frames must have a unique title attribute”
- WCAG
- 4.1.2 Name, Role, Value (opens in a new tab) · Level A · since WCAG 2.0
- Other standards
- EN 301 549 9.4.1.2 · RGAA 2.2.1
- Last reviewed
- 14 October 2026