For each frame that has a frame title, is this frame title relevant?

A screen reader lists the frames on the page before the user enters them. If your <iframe> displays title="YouTube video player", the user knows there's a video player — but not which one, or why it's there. A relevant title is what allows them to decide whether to enter that frame or not.

This criterion applies only to frames that already have a title attribute — criterion 2.1 checks for the presence of that attribute. Here, we verify whether that title says something useful. An empty, generic, or identical title across all frames on a page does not pass. A generic title is like having no title at all.

In practice: if you embed a product demo video, write title="Video tutorial: installation in 3 steps" rather than title="YouTube video player". For a map, title="Map showing our office location" is much better than title="Google Maps". The title should describe the nature of the embedded content, not just the platform delivering it.

Un test to assess the relevance of frame titles

Relevance of title on <iframe> and <frame>

  1. Identify all <iframe> and <frame> elements on the page.
  2. For each frame that has a title attribute, read the value of that attribute.
  3. Verify that this value describes the nature or purpose of the frame in a way that is understandable outside of visual context.
  4. A title is not relevant if it is empty, generic ("frame1", "iframe", "YouTube video player"), or identical across frames with different content.
  5. If all frames with a title have a relevant title, the test is validated. A single non-relevant title is enough to fail the test.

Examples

❌ Non-compliant : Generic frame title copied from YouTube embedding code

<iframe
  src="https://www.youtube.com/embed/dQw4w9WgXcQ"
  width="560"
  height="315"
  title="YouTube video player"
  allowfullscreen>
</iframe>

The title reproduces word-for-word the default text provided by YouTube. A screen reader user navigating between frames on the page hears "YouTube video player" — they know there's a YouTube player, but not which video it contains or why it's on this page. They must enter the frame to discover this, which can represent significant cognitive load if there are multiple frames.

✅ Compliant : Frame title describing the specific video content

<iframe
  src="https://www.youtube.com/embed/dQw4w9WgXcQ"
  width="560"
  height="315"
  title="Video tutorial: set up your account in 3 steps"
  allowfullscreen>
</iframe>

The screen reader user immediately knows what this frame contains before entering it. They can choose to navigate it or skip it based on their needs. The title describes the nature and subject of the embedded content, not the platform delivering it.

Tips and pitfalls

⚠️ Pasting YouTube embedding code without modifying the title

YouTube automatically generates title="YouTube video player" in its embedding snippet. This is the most frequent error in auditing this criterion: developers paste the code without touching the attribute. Systematize replacing this value from the moment of integration, for example through a centralized component that makes a title mandatory.

⚠️ Generic title acceptable when adjacent context is explicit

Debate exists within the RGAA auditing community: if an <h2> title directly precedes the iframe and describes the video precisely, a title="YouTube video" may be judged sufficient. Technique H64 specifies that an iframe's title "does not label the content, but indicates the purpose of the frame". The safest approach during an audit remains the specific title, especially for video series where context may be ambiguous.

💡 Audit using the screen reader's frame navigation

With NVDA, press F to navigate from frame to frame. With VoiceOver, open the rotor and select "Frames". Navigate only through the frames without entering them: if you understand what each iframe contains just by listening to its title, the titles are relevant.

⚠️ Multiple iframes with the same title on one page

If a page embeds three YouTube videos with title="YouTube video", the user cannot distinguish them in the frame list. Each title must be unique and specific to its frame's content. Two identical iframes in nature can coexist, but their titles must differentiate them.

⚠️ Technical hidden iframes are out of scope

An <iframe> used for tracking or loading third-party scripts with display:none or visibility:hidden is not rendered by screen readers. These invisible frames are outside the scope of criterion 2.2. However, if they carry a title, an automated auditing tool may still flag it.

Frequently asked questions

How should you formulate a video or external page iframe title according to RGAA 2.2?

No, not word-for-word — but it must convey the essentials. The goal is for the user to understand what they will find in the frame before entering it. A title="YouTube video: set up your account" is sufficient, even if the video's full title is longer. Aim for clarity, not exhaustiveness.

How do you audit criterion RGAA 2.2 on the relevance of iframe title without a screen reader?

Open DevTools and type document.querySelectorAll('iframe[title], frame[title]') in the console. Inspect each title attribute returned. A title is not relevant if it is generic, identical across multiple frames, or does not describe the content. Note that automated tools detect missing title attributes (criterion 2.1) but cannot evaluate relevance (criterion 2.2) — this is a mandatory manual check.

Why is title="YouTube" not sufficient for a video iframe according to RGAA criterion 2.2?

No, according to the majority interpretation of the RGAA glossary, which requires that the title reflect the "nature of the content". "YouTube" identifies the platform, not the video. A minority of auditors accepts a generic title like title="YouTube video" if the page context is very explicit. When in doubt, opt for the specific version: title="YouTube video: [video subject]".

How does RGAA criterion 2.2 apply to an iframe without a title attribute?

It doesn't. Criterion 2.2 concerns only frames that already have a title attribute. The absence of title falls under criterion 2.1. A frame without a title fails criterion 2.1 but is outside the scope of criterion 2.2.

How does RGAA criterion 2.2 apply to HTML4 frameset <frame> elements?

Yes, the criterion text explicitly mentions <frame> and <iframe> elements. HTML4 framesets have nearly disappeared by 2024, but if you encounter one during an audit, the same rules apply. The relevance of the title is even more critical in this context, as older screen readers allowed dedicated frame-by-frame navigation.

References

RGAA 4.1.2: Criterion 2.2
WCAG 2.1:4.1.2 (A)H644.1.2 (A)