Public documentation
Installation and setup
How users should load, verify, update, and remove the Chrome extension build.
Release status
These instructions are for the repository extension build. Do not claim Chrome Web Store approval or production release status unless a release note and store record explicitly prove it.
Prerequisites
- A Chromium-family browser that supports Manifest V3 extensions.
- A trusted copy of the extension package or repository checkout.
- Permission to review the target pages and handle any exported evidence.
- Awareness that browser-restricted pages and some enterprise-managed contexts may block injection.
Load the extension
- 1
Build or obtain the package
Use the repository-supported extension build output or an approved extension package. Do not use legacy bookmarklet instructions for the extension.
- 2
Open the browser extensions page
Open
chrome://extensionsor the equivalent Chromium extensions manager. - 3
Enable developer mode
Developer mode is required for local unpacked extension testing.
- 4
Load the unpacked extension
Select the built extension directory, normally
dist-extensionfor release-style local testing. - 5
Verify the action button
Pin or open the A11Y Cat action and run a smoke scan on an authorised test page.
Update and removal
| Task | Action | Evidence to keep |
|---|---|---|
| Update extension build | Rebuild or replace the package, then reload the extension in the browser manager. | Package source, commit, browser version, and smoke-scan result. |
| Remove extension build | Remove the extension from the browser manager. | Record any exported evidence retained outside the browser. |
| Clear local data | Use the extension local data controls where supported, then remove exported files according to your policy. | Clear-data action date and retained export location if applicable. |