Fix guide · Embeds without a title

How to fix “Frames must have an accessible name”

By · Updated

An embedded map, video or widget sits in an iframe with no title. Add a title attribute to the iframe that says what's inside, like title="Map to our office".

axe rule
frame-title
WCAG
4.1.2 Name, Role, Value (Level A)
Lighthouse
Google Lighthouse and PageSpeed Insights report it as “<frame> or <iframe> elements do not have a title”

What it means

Embeds from Google Maps, YouTube, booking tools and chat widgets arrive in an iframe, a little window onto another site. Screen reader users can jump between frames by name. With no title, Deque notes, a screen reader falls back to saying things like "frame", the file name or the web address.

Embed codes copied from another service often leave the title out, and if the embed is in a site footer it fails on every page at once.

Who it affects

People who use a screen reader.

How to find it

  1. Run the free checker. Each iframe it lists shows the start of its src, which tells you whose embed it is.
  2. Look at your contact page map, any video, and booking or review widgets.

How to fix it

  1. Add a title attribute to the iframe tag in the embed code, describing the content in a few words.
  2. If a plugin writes the iframe for you, look for a title setting in the plugin. If there isn't one, ask its maker, or wrap the embed in custom code.
  3. Make titles unique when a page has more than one embed.

A map embed

Before · fails
<iframe src="https://www.google.com/maps/embed?pb=..."
  width="600" height="450" loading="lazy"></iframe>
After · fixed
<iframe src="https://www.google.com/maps/embed?pb=..."
  width="600" height="450" loading="lazy"
  title="Map to our office"></iframe>

From a real fix

On the law firm site I fixed, a Google Maps embed in the site footer had no title, so the same failure showed up on every page I checked. Adding the title where the footer prints the map fixed all of them at once.

What a scanner can and can’t tell you

Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.

Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.

Sources

All checked November 8, 2026. The rule wording is axe-core 4.14.0’s own.

Related fixes

Every fix guide →

Check a page for free

Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.

Run the free checkno sign up · one page at a time

Rather have someone fix it for you? Tell me about your site.