iFrame Accessibility Reference Guide (WCAG 2.1 AA)

Why this matters

<iframe> embeds are common (maps, videos, forms, third-party tools). Without accessible setup, they can be confusing or unusable for screen reader and keyboard users. The most common failure is missing an accessible name.

Quick QA checklist (dev/test)

Before publishing, confirm:

• iframe has a descriptive title

• iframe is introduced with nearby context (heading/short text)

• fallback link is provided (maps/forms/tools)

• responsive layout works at 320px width and at 200% zoom

• no autoplay surprises

• page still works with keyboard only (Tab/Shift+Tab)

• (If form/video) captions and form fields are accessible in the embedded experience