Frame Title Unique

Each <frame> or <iframe> element must include a unique, descriptive title attribute so assistive technology can tell them apart.

Frames act as separate user-interface components. Without a distinct accessible name, screen-reader users hear identical entries such as “frame” or a repeated title and cannot decide which one to open. Giving every frame a clear, unique title attribute (or an equivalent ARIA label) solves this problem and supports reliable programmatic identification.

Pass Patterns

Frame has a descriptive unique title

A clear, specific title for every frame makes them distinguishable.

HTML

<iframe
    src="https://weather.example.com/new-york"
    title="New York City weather forecast">
</iframe>
<iframe
    src="https://weather.example.com/london"
    title="London weather forecast">
</iframe>

Fail Patterns

`<iframe>` elements with different content share the same name

The same title appears twice, leaving users with no way to know which frame is which.

HTML

<iframe
    src="https://weather.example.com/new-york"
    title="Weather forecast">
</iframe>
<iframe
    src="https://weather.example.com/london"
    title="Weather forecast">
</iframe>

Try It Yourself

New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers

Load the page and open a screen reader.
Open the screen reader’s element list (for example, NVDA + F7 on Windows or VO + U on Mac).
Choose the frames or landmarks view (depending on where iframes are listed in your screen reader).

Expected result: Iframes have distinct titles, letting you jump directly to the desired frame.

Actual result: The list shows duplicated <iframe> names, forcing trial-and-error navigation.

FAQ

How does this issue relate to 4.1.2 Name, role, value?

SC 4.1.2 requires every user-interface component to expose a programmatically determinable name. The title attribute (or an ARIA label) supplies that name for frames, making each one discoverable and operable through assistive technology. When different iframe elements have a similar or an undescriptive name their discoverability is compromised.

Why is this issue marked as Serious?

Without unique titles, screen-reader users cannot reliably navigate between frames, leading to confusion, wasted time, and potential task failure. Because major browsers and assistive technologies depend on the accessible name to list and enter frames, the impact spans all platforms and significantly harms usability.

Standards and Regulations

Standard	Success Criterion	Reference
WCAG 2.2	4.1.2 Name, Role, Value (A)	For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to assistive technologies.
EN 301 549	9.4.1.2 Name, Role, Value	Same as the WCAG text.

Personas impacted by this issue

frame-title

frame-title-unique