Google Maps Embed Accessibility: What to Fix

An embedded map is a separate document loaded inside your page through an iframe element. A sighted visitor sees streets and a pin at a glance. A screen reader user hears only what your page code says about that frame, and a keyboard user must be able to move into the map and back out again. Google Maps embed accessibility comes down to three jobs on your side of the code: name the frame, repeat the location facts in plain text, and test the keyboard path.

Key takeaways

• Give every map iframe a title naming the place and purpose, such as "Map showing the shop location on Main Street".
• Put the street address and opening hours in real text on the same page, under a heading a reader can find.
• Test with a keyboard only: Tab into the map, Tab out of it, and Shift plus Tab back.
• If focus stays inside the map and you cannot move past it with the keyboard alone, treat that as a trap to work around on your page.

Give the frame a clear title

The title attribute on an iframe is the frame's accessible name, the short label assistive technology announces before a user enters the frame. W3C technique H64 describes this use of the title attribute, and it relates to WCAG success criterion 2.4.1, Bypass Blocks, and to success criterion 4.1.2, Name, Role, Value, at Level A. A user should know what is inside the frame before deciding to enter it.

A pasted embed code often arrives with no title. Check the code you pasted, and edit the attribute yourself. The name attribute is not a substitute. W3C technique H64 is clear on this point: title labels the frame for users, while name labels it for scripting and is not presented to the user.

The failing version has no title at all:

<iframe src="https://www.google.com/maps/embed"></iframe>

The passing version names the place and the purpose:

<iframe src="https://www.google.com/maps/embed" title="Map showing the shop location on Main Street"></iframe>

Write the title for the person who will hear it. A title that reads "map" tells a listener nothing they can act on. If a page holds more than one map, give each one a different title. After you save, open the page source and confirm the title survived, since embed blocks sometimes strip attributes on save.

Put the same facts in text beside the map

A title names the frame. It does not carry the address, the hours, or the directions. A screen reader user cannot read a pin or a street layout from the picture alone, so the page needs the same facts in text, next to the map.

WCAG success criterion 1.1.1, Non-text Content, calls for a text alternative for non-text content, and success criterion 1.3.1, Info and Relationships, calls for information shown by presentation to be programmatically determined or available in text. For a location map, put the facts under a heading such as "Visit us", then list the street address and opening hours in real text, not in an image and not only inside the map.

<h2>Visit us</h2>
<address>Shop on Main Street, Springfield</address>
<p>Open weekdays and Saturday. See the opening hours on this page for holiday changes.</p>

That example uses placeholder wording. Replace it with your real address and real hours. Add a phone number in text if callers need one, and a written directions link if you have a directions page of your own. Do not write directions that depend on the map picture, such as "turn left at the blue line". Place the text before the map in reading order when you can. The text also helps when the map fails to load: the address and hours stay on the page.

Google Maps embed accessibility: check the keyboard path

A map embed can hold keyboard focus in ways a mouse user never notices. WCAG success criterion 2.1.1, Keyboard, at Level A, requires functionality to be available from a keyboard interface. Success criterion 2.1.2, No Keyboard Trap, at Level A, states the rule: if focus can be moved to a component with a keyboard, focus can be moved away using only a keyboard, and if exit needs more than unmodified arrow or Tab keys, the user must be told the exit method.

Run this check on your own page, with a mouse set aside:

• Press Tab from the content above the map until focus reaches the map frame, and note what is announced or outlined.
• Keep pressing Tab, and note whether focus reaches the next link or button on your page.
• Press Shift plus Tab to move back, and note whether focus returns to the content before the map.
• Try the arrow keys inside the map, and note what they do on your embed. Do not assume they behave the same on every embed or in every browser.

If focus reaches the next element, the path is open. If focus circles inside the map, or if you need the mouse to get out, the page has a keyboard trap at that spot. Check the frame first: confirm the title is present, and confirm the text alternative sits in the normal Tab order so a keyboard user can reach the address without entering the map.

If the map is redundant because the full address, hours and directions already sit in text beside it, some authors hide that duplicate frame from assistive technology. Yale guidance allows that choice only when the frame is purely decorative or redundant. Do not hide a map that is the only source of the address or directions. If the trap sits inside the hosted map, put the text alternative first in the order and add a link before the map that jumps to that text.

Common mistakes

• Pasting embed code without reading it, so the frame ships with no title or a generic title.
• Using the same title on every map on a page, so a frame list reads as repeats.
• Putting the address only inside the map, or only in an image of a map, with no text version.
• Writing hours that differ from the hours in the map listing.
• Assuming a mouse test proves the keyboard path works.
• Adding a title and stopping there, without the text alternative and the Tab in and Tab out check.

How Axeazy helps with this exact issue

Axeazy lists iframe titles among the 14 fix categories it works on. A scan can flag a missing or empty title in the iframe code on your own page, which is the part of a map embed you control. Read the honest scope on the capabilities page, and read how the scan works to see how findings are recorded with a date and time.

For a site with its own GitHub repository, fixes arrive as a real pull request with a visible code diff for review and merge. For other sites, the scan gives the computed fix values and a guided checklist to apply by hand.

Be clear about the limit that matters for maps. Axeazy does not scan content behind logins or on third party hosted embeds the scanner cannot reach, so it cannot reach inside the hosted map to change its inner controls. The frame title, the text alternative, and the keyboard check stay with you, and a quick manual keyboard and screen reader check is part of good practice after any scan.

For the wider frame topic, see the iframe title guide on our blog.

Want a quick read on your own site? Run Axeazy's free 60 second scan . It needs no signup.

Last checked: October 26, 2026.

FAQ

Does a Google Maps embed need a title if the address is already in text nearby?

Yes. The title and the text alternative do different jobs. The text gives the address and hours, while the title names the frame.

What should a good map frame title say?

It should name the place and purpose in a few words, such as "Map showing the shop location on Main Street". Avoid a single generic word such as "map", and avoid repeating the same title on two different maps.

How do I test for a keyboard trap in my own map embed?

Put the mouse aside, press Tab until focus reaches the map, keep pressing Tab, and watch for the next link or button on your page. Then press Shift plus Tab to move back. If focus never reaches the next element, work around it on your page with the text alternative and a link to it.

Can Axeazy fix the controls inside a Google Maps embed?

No. Axeazy can flag a missing title in the iframe code on your page, and it can record that finding with a date and time. It cannot reach inside a third party hosted map to change its inner controls.

Sources

• W3C Technique H64: Using the title attribute of the frame and iframe elements, checked October 26, 2026
• W3C Understanding Success Criterion 2.1.2: No Keyboard Trap, checked October 26, 2026
• Yale Usability and Digital Accessibility: Internal Frames, checked October 26, 2026
• Accessibility Insights: frame-title, checked October 26, 2026