Accessibility Wiki

Frames must have a descriptive title

Rule frame-title · Document, language & navigation · impact serious · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters

Screen-reader users land on an iframe and hear only "frame" — without a title they must enter it to find out whether it holds a video player, a map, or an ad. A generic name ("frame", "widget", a URL) is as unhelpful as none.

How to fix

Add title="…" naming the frame’s content (e.g. "Product demo video"). Hide purely decorative or tracking frames with aria-hidden="true" and tabindex="-1".

Example

✕ Fails
<iframe src="https://maps.example.com/store"></iframe>
✓ Passes
<iframe src="https://maps.example.com/store" title="Map of store locations"></iframe>

Example

✕ Fails
<iframe src="/player" title="frame"></iframe>
✓ Passes
<iframe src="/player" title="Product demo video"></iframe>

WCAG success criteria

4.1.2 Name, Role, Value — Level A

Every UI component must expose a correct name, role, and (where relevant) state/value to assistive technology.

Understanding 4.1.2

2.4.1 Bypass Blocks — Level A

Provide a way (skip link, landmarks, headings) to bypass repeated blocks like navigation.

Understanding 2.4.1

Standards

This rule contributes to the following standards:

WCAG A EN 301 549 Section 508 Trusted Tester

Standard Criteria
Section 508 1194.22(i)
EN 301 549 9.4.1.2, 9.2.4.1
Trusted Tester v5 12.d

References