Public documentation
FAQ
Concise answers to common release, privacy, scanner, and workflow questions.
Frequently asked questions
Does A11Y Cat prove WCAG conformance?
No. It supports accessibility review with automated and guided evidence. Full WCAG conformance requires broader expert testing and review.
Does it replace manual testing?
No. Manual review, keyboard testing, real assistive technology testing, responsive testing, and user-task testing remain required where relevant.
Does Screen Reader Review replace NVDA, JAWS, VoiceOver, TalkBack, or Narrator testing?
No. It is an aid for organising review evidence and planning manual assistive technology testing.
Does the extension send scan data to a developer server?
The documented extension package does not declare a developer-operated scan server, analytics pipeline, telemetry endpoint, hosted AI API, or remote axe-core CDN for scan processing.
Why are some findings marked needs review?
Some evidence requires human judgement, visual inspection, interaction, or assistive technology testing before it can be treated as a defect.
Why is contrast sometimes routed to review?
Gradients, images, transparency, overlays, dynamic backgrounds, CSS effects, text over media, decorative/logo text, and third-party overlays can make automated contrast evidence uncertain.
Can image-only design review identify DOM or ARIA failures?
No. It can discuss visible design risks, but it cannot verify selectors, focus order, ARIA, accessible names, semantic HTML, form labels, or screen reader output from an image alone.