A11yInspect

A11yInspect

A free browser extension that automatically scans web pages for accessibility problems against WCAG and other standards, highlighting the exact code causing each issue.

🔗 Visit A11yInspect
📁 Editors, IDEs & Dev Tools🗣️ English📅 August 24, 2026

Description

Checking whether a webpage is accessible to people using screen readers or keyboard navigation used to mean either learning WCAG's dense rulebook by heart or paying a consultancy to audit every page. A11yInspect is a free browser extension that does a big chunk of that checking automatically, right in the browser tab you're already looking at, and highlights exactly which piece of code is causing which problem.

It runs 600+ automated checks across 30 WCAG success criteria (plus Section 508, EN 301 549, and India's GIGW 3.0/IS 17802 standards), with a claimed sub-1% false positive rate, and ships bookmarklets for quick checks like tab order, color contrast, and text spacing. The free tier covers unlimited page testing; the $120/year Pro tier adds a dashboard, screenshot capture, and downloadable audit reports, and Enterprise adds Jira/GitHub integration and custom standards. It's made by BarrierBreak, a 20+ year accessibility firm, and is also available as a VS Code extension and ESLint plugin for catching issues before code ships.

💬 Our review

The short version: for a developer or QA tester who wants to catch obvious accessibility problems before a page ships, A11yInspect's free tier is a genuinely useful daily-driver browser extension, backed by a company that does nothing but accessibility.

Against the two most common free alternatives — axe DevTools and Google Lighthouse's accessibility audit, both also free and widely used — A11yInspect's pitch is breadth (600+ checks across more standards, including region-specific ones like India's GIGW) and a lower false-positive rate, though none of the three replace a human accessibility review for judgment calls like whether alt text is actually meaningful. The VS Code extension and ESLint plugin are a real differentiator if you want issues flagged while writing code rather than after deploying, but pricing and feature details for those aren't published clearly, so budget time to test them yourself. For most developers, running it alongside axe DevTools costs nothing and only adds coverage; teams needing WCAG certification or Jira-integrated workflows should look at the paid tiers or a dedicated audit service.

💰 Pricing

FreemiumFree: unlimited page testing, bookmarklets, contrast checker. Pro: $120/year, dashboard + reports. Enterprise: custom pricing.
Free 0Pro 120

📊 Global score

45Average
🌐Availability15/100Faible

1 language · 0 platform

📄Profile75/100Bien

Profile completeness

🤖 AI-enriched data

💰 Pricing model
🆓 Freemium

Extension navigateur gratuite : test de pages illimité, bookmarklets, vérificateur de contraste. Pro 120$/an : test par nœud, tableau de bord, captures d'écran, rapports d'audit (essai 30 jours). Enterprise : sur devis (normes personnalisées, intégration Jira/GitHub).

👥 Target audienceDéveloppeurs, testeurs QA, professionnels de l'accessibilité, entreprises intégrant l'accessibilité au workflow de développement
🗣️ Languagesen
🌍 Target countriesWorldwide
👍

Pros

600+ vérifications couvrant WCAG, Section 508, EN 301 549 et normes régionales (GIGW, IS 17802)

Taux de faux positifs revendiqué inférieur à 1%

Gratuit avec test de page illimité sur le plan de base

Disponible aussi en extension VS Code et plugin ESLint pour détecter les problèmes avant déploiement

Éditeur spécialisé avec 20+ ans d'expérience en accessibilité

👎

Cons

Plan Pro payant (120$/an) pour tableau de bord et rapports téléchargeables

Détails de tarification peu clairs pour l'extension VS Code et le plugin ESLint

Un outil automatisé ne remplace jamais une revue humaine pour les cas de jugement

Fonctionnalités Enterprise réservées à un devis sur contact commercial

❓ Frequently asked questions

What is A11yInspect in one sentence?
Is A11yInspect free?
Which browsers does it support?
Can it catch issues before I deploy code?
Is it worth the money compared to alternatives?
Which tool should you pick for your case?