These docs are for CORA 0.10, an older release. Read this page in the newest docs.
Frames need to be checked too
- Rule:
axe/frame-tested - Checks: Frames should be tested with axe-core
- WCAG: none; a best practice, not a WCAG success criterion
- Fix class:
manual: A fix needs a person to work out what to change, beyond authored text or a visual decision.
Who it affects
Section titled “Who it affects”- People who use a screen reader or a braille display, most of them blind.
- People who use a keyboard or a switch device instead of a mouse.
How to fix it
Section titled “How to fix it”axe could not run inside the frame
Section titled “axe could not run inside the frame”This reports a gap in what the scan covered, not a fault in the markup: nothing inside the frame was checked. Scan the frame’s own address as a page of its own, or check its content by hand.
The frame was still loading, or failed to load, when the scan reached it
Section titled “The frame was still loading, or failed to load, when the scan reached it”Check that the frame loads where the scan runs, such as with the same sign-in and network access, then scan again.
Fixes that fail
Section titled “Fixes that fail”Reading the page’s results as covering the frame
Section titled “Reading the page’s results as covering the frame”Nothing inside the frame was checked, so its issues are unknown, not absent. cora lists such a frame in its coverage with the reason frame-not-scanned.
More on the rule
Section titled “More on the rule”axe-core’s documentation of the rule
CORA’s fix guidance adapts content from accessibility-agents, under the MIT License: see its notice.