This check finds <frame> or <iframe> elements without a meaningful title attribute. The title should identify the embedded experience, not repeat a generic word such as “frame.”
Why this matters
A screen-reader user needs to decide whether to navigate into embedded content. A descriptive title distinguishes a video player, payment form, map, support widget, or other frame without requiring the user to explore it first.
How to fix it
- Add a short title that states the embedded content or task, such as
title="Product demo video". - Give repeated frames distinct titles when their contents differ.
- Remove obsolete or empty frames that no longer support the page.
- Do not rely on the iframe’s internal page title because it may not label the outer browsing context.
When the finding appears across many URLs, fix the shared component or layout that produces it instead of patching generated HTML page by page. Recheck representative templates and responsive states after deployment so the correction does not create a regression elsewhere.
How to verify the fix
Inspect all rendered frames, including those added after consent or interaction. Confirm the accessible name is specific and remains accurate when the embedded source changes.
Keep before-and-after evidence for the affected URL, original output, correction, and verification method. If markup changes after load, test consent states, localization, responsive variants, and client-side navigation because the initial HTML and rendered DOM can differ.