Public documentation
Technology stack
Libraries, browser APIs, local bundles, and privacy impact for the documented extension package.
Runtime stack
| Area | Technology or library | Used for | Shipped? | Boundary |
|---|---|---|---|---|
| Extension platform | Chrome Extension Manifest V3 | Action button, service worker, scripting, storage, packaging | Yes | Browser platform; data handling depends on extension code and user exports. |
| Launch and permission | chrome.action and activeTab | User-triggered active-tab access | Yes | Temporary tab access after explicit user action; no broad host permissions in the release manifest. |
| Injection | chrome.scripting | Inject packaged local scripts into the active tab | Yes | Uses extension files, not remote scripts. |
| Automated scan engine | axe-core 4.11.x | WCAG-tagged automated rule evaluation | Yes, as vendor/axe.min.js | Local bundle; no remote CDN. |
| Custom modules | A11Y Cat runtime modules | Result shaping, metadata, links, language, spelling, headings, contrast, diagnostics, exports, history | Yes after build | Source-labelled separately from axe-core. |
| Spelling | CSpell-derived local engine and dictionaries | English spelling review with allowlist support | Yes | No remote spellcheck API; unsupported languages are skipped or review-only. |
| Screen Reader Review aid | Guidepup virtual screen reader bundle | Virtual review support and interaction logs | Yes | Review aid only; not real AT validation. |
| Docs | Static HTML, CSS, and small local JavaScript | Public technical guide on GitHub Pages | No extension runtime impact | No analytics or remote runtime declared for docs. |
What is not used in the documented scan path
- No developer-hosted server for scan processing.
- No developer database for scan results, reports, browsing activity, or history.
- No analytics or telemetry endpoint in the documented extension package workflow.
- No hosted AI API in the extension scan path.
- No remote axe-core CDN; axe-core is bundled locally.
- No remote spellcheck API; spelling uses bundled local assets.
- No server-side scanning.