What This Rule Checks
Ensures <iframe> and <frame> elements contain the axe-core script
Who Is Affected
This issue primarily affects: Sighted Keyboard Users users, who can see the screen but navigate exclusively with a keyboard; Blind users, who rely entirely on screen readers or braille displays to navigate and interact with content; Deafblind users, who rely on braille displays and cannot access visual or auditory content.
Why This Matters
This rule flags iframes whose content has not been tested for accessibility. Untested embedded content may contain violations that affect the overall page experience. This is an axe-core internal rule; ACE retains it as a best practice reminder.
Code Examples
<!-- Frame content not tested for accessibility -->
<iframe
src="third-party-widget.html"
title="Widget">
</iframe>
Copy
<!-- Ensure iframe content is accessible -->
<iframe
src="accessible-widget.html"
title="Customer feedback form">
</iframe>
<!-- The embedded page should also pass accessibility checks -->
Copy
Common Mistakes to Avoid
- Assuming third-party iframe content is accessible without testing.
- Not including accessibility testing tools in embedded content.
- Ignoring iframes during accessibility audits.
Tip: Proper document structure enables assistive technologies to present content meaningfully. Headings, lists, and semantic HTML elements create a navigable outline of the page that screen reader users depend on.