Public documentation
Supported environments
Browser, page, permission, and runtime boundaries for the documented extension package.
Environment matrix
| Environment | Status | Notes |
|---|---|---|
| Chrome / Chromium MV3 | Primary target | Use the current extension package and verify against representative pages. |
| Microsoft Edge Chromium | Likely compatible, verify locally | Chromium behaviour is similar but enterprise policy and extension settings can differ. |
| Firefox | Not the primary published extension target | Adaptation notes exist, but do not claim supported release unless a release package proves it. |
| Browser-restricted pages | Unsupported or limited | Extension stores, browser settings, PDF viewers, and privileged pages can block injection. |
| Authenticated or enterprise apps | Supported only where authorised and technically accessible | Review role, state, and data-handling boundaries before scanning. |
| Cross-origin iframes and embedded widgets | Limited | Test embedded experiences separately where authorised. |
Runtime boundaries
A11Y Cat can inspect only contexts where the browser allows the extension to run. Iframes, shadow DOM, strict CSP, cross-origin content, dynamic states, and pages requiring user interaction can reduce coverage.
Verification required for each environment
- Record browser name and version, extension package source, operating system, viewport class, authentication state, and target page type.
- Run a smoke scan on a known page before relying on output.
- Review diagnostics and limitations before making coverage claims.
- Repeat scans after opening menus, dialogs, errors, responsive states, or authenticated journeys that matter.