Store submission support
Chrome Web Store submission support materials
Use this page to fill listing, privacy, and distribution fields accurately. It supports submission preparation only; it is not proof that Chrome has approved the extension.
Store listing copy
| Extension name | A11Y Cat |
|---|---|
| Short description | Run local accessibility checks on the active page and export evidence for developer and QA review. |
| Detailed description | A11Y Cat supports accessibility review by running automated checks on the active tab after user action, grouping confirmed issues separately from manual-review evidence, and exporting reports for remediation handoff. It includes metadata, headings, language, alt text, broken link, browser preference, keyboard/focus, and virtual screen-reader review support where available. Automated and virtual review output does not replace manual accessibility testing or real assistive-technology validation. |
| Single purpose statement | Support accessibility review of the current active page after user action through local checks, guided review workflows, and user-controlled exports. |
| Recommended category | Developer Tools |
| Language | English |
Privacy tab answers
- Local-first scanning: page URL, title, DOM evidence, selectors, snippets, notes, settings, scan history, and virtual review state may be processed and stored locally in the browser.
- User-controlled exports: CSV, JSON, diagnostics, screenshots where captured, and HTML QA reports are created only after user action.
- No telemetry or analytics are declared for the documented extension scan path.
- No remote executable code is declared. Extension logic, axe-core, and virtual review support must be packaged locally in the submitted extension.
- Privacy policy URL: https://carlashub.github.io/a11y-cat-extension/docs/privacy-policy.html.
Permissions justification
| Permission | Justification | Submission note |
|---|---|---|
| activeTab | Allows the extension to inspect the current tab only after the user invokes it. | Core to the single-purpose active-page review workflow. |
| scripting | Injects packaged scanner and panel runtime into the active tab after user action. | Required for current-page checks and UI. |
| storage | Saves settings, scan history, notes, and local review state in browser storage. | Disclose local storage and clearing controls. |
| debugger | Supports browser-level QA controls and emulation evidence that Chrome extension APIs otherwise cannot observe or apply reliably. | Sensitive permission. The final Web Store submission should include a clear reviewer note explaining why it is required and how activation is user-scoped. |
Screenshots and animated previews
Public media shows the A11Y Cat panel only. The assets are documentation and listing-support material for the extension interface, not audit results for a specific website.
- Scan Results screenshot, 980 x 940
- Metadata Check screenshot, 774 x 808
- Heading Structure screenshot, 774 x 319
- Alt Text Analysis screenshot, 774 x 562
- Language mismatch screenshot, 774 x 730
- Broken links screenshot, 774 x 989
- Browser Preference QA Controls screenshot, 806 x 858
- Screen Reader Review screenshot, 806 x 966
- Scanner workflow GIF, 900 x 1120
- Guided review GIF, 900 x 1120
Known limitations and required human approval
- The owner must regenerate and inspect the final Chrome Web Store ZIP immediately before upload.
- The owner must approve the Chrome Web Store support email/contact and distribution settings.
- The debugger permission needs explicit human approval and a concise reviewer explanation.
- Automated checks do not detect all accessibility issues and do not prove WCAG compliance.
- Virtual Screen Reader Review output is Guidepup/virtual evidence and browser TTS playback where enabled, not proof from NVDA, JAWS, VoiceOver, TalkBack, or Narrator.
Public repository boundary
This public repository contains documentation, support pages, privacy pages, and approved public assets only. It must not expose private implementation code, backend/test files, local QA evidence, environment files, internal plans, or generated release ZIPs.