Frames should be tested with axe-core
Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
Semantic structure communicates relationships and hierarchy to assistive technologies and keyboard navigation.
How to fix this issue
Apply semantic HTML, provide programmatic names, ensure keyboard access, and validate against WCAG 2.2.
Developer guidance
Enforce these rules in your component library and CI (eslint, jsx-a11y, jest-axe). Validate with keyboard-only and screen reader tests.
Code examples
Incorrect Implementation
<iframe src="/widget.html"></iframe>Correct Implementation
<iframe src="/widget.html" title="Sales dashboard widget"></iframe>
Trusted by organizations across Europe working toward WCAG and EAA conformance