Public documentation
Known limitations
What the extension cannot inspect, prove, or certify without additional human review.
Limitations matrix
| Limitation | Why it matters | Recommended action |
|---|---|---|
| Current page state only | A scan reflects the rendered state at the time of inspection. | Review additional routes, states, breakpoints, roles, errors, and authenticated flows manually. |
| Restricted browser contexts | The browser can block extension access to privileged pages and stores. | Use diagnostics and alternate test methods. |
| Iframes and cross-origin content | The extension may not inspect all embedded content. | Test embedded experiences separately where authorised. |
| Dynamic and interactive components | Menus, dialogs, validation, and async updates may not appear in the scanned state. | Exercise components manually and rerun scans after state changes. |
| Contrast uncertainty | Gradients, background images, transparency, overlays, dynamic backgrounds, CSS effects, text over media, decorative/logo-like text, and third-party injected widgets can make contrast evidence uncertain. | Treat uncertain output as contrast review or diagnostics, not confirmed scanner failures. |
| Image-only design review | Imported PNG, JPG, or WebP screenshots do not expose DOM structure, selectors, keyboard focus order, ARIA, accessible names, semantic HTML, tab order, form labels, or real screen reader output. | Label findings as visual/design review and verify implementation details in the built product. |
| Language and spelling support | Short, mixed-language, unsupported-language, and brand-heavy content can reduce confidence. | Use language/spelling output as review evidence, then verify with human language QA. |
| Assistive technology behaviour | The Screen Reader Review aid does not replace real AT testing. | Run NVDA, JAWS, VoiceOver, TalkBack, keyboard-only, and other required testing for release decisions. |
| WCAG conformance | Automated/guided evidence is incomplete by design. | Use A11Y Cat as evidence support, not a conformance certificate. |
How limitations appear
Limitations may appear in scan summaries, diagnostics, review queues, or exports. They should be recorded in release evidence because they explain where manual verification is required.