Public documentation

Troubleshooting

Practical diagnostics for install, scan, export, and unsupported-context failures.

Common failures

Problem	Likely cause	Action
Extension action does not run	Extension not loaded, wrong build directory, browser policy, or unsupported page.	Check extension manager, reload the package, and test on a simple authorised page.
Scan blocked	Restricted browser page, extension store, PDF viewer, cross-origin frame, or CSP/runtime constraint.	Review diagnostics and use another test method.
No or low result count	Page state did not expose the target content, route requires interaction, or scan happened before dynamic content loaded.	Open the relevant state and rescan.
Contrast result looks uncertain	Complex background, overlay, gradient, media, transparent layer, or third-party injected widget.	Use manual visual review and record the uncertainty before filing a defect. Contrast Inspector is roadmap work and is not exposed in the active extension.
Export missing expected module evidence	Module was not selected, item-level report inclusion was not set, or evidence was review/unable rather than confirmed.	Review module controls and explicit Add to QA report state.
Screen Reader Review output is incomplete	Aid does not represent real AT or page interaction state changed.	Use real AT testing and record differences.

Collect useful support evidence

Extension version and package source.
Browser name/version and operating system.
Page type, route, authentication state, and whether the page is restricted.
Steps to reproduce from a fresh tab.
Diagnostics export if safe to share.
Expected and actual behaviour.
Whether the issue affects confirmed results, review queues, diagnostics, storage, or exports.