Announcing A11yEngine to the community
Hello everyone 👋,
I've been building A11yEngine - A Chrome extension that goes beyond just finding accessibility violations and actually fixes them.
Most accessibility tools (Lighthouse, axe DevTools, etc.) give you a list of issues and leave you to figure out the rest.
A11yEngine closes that loop.
What it does differently:
🔍 Dual-engine scanning combines axe-core with a custom heuristics engine that catches issues axe misses: broken SPA focus resets, missing skip links, chatty live regions, PDF accessibility, WCAG 2.2-only criteria, and more
🤖 AI code fixes for every violation, it generates a ready-to-paste fix in React, Tailwind, or Vue
💸 Revenue-blocker tagging flags violations on checkout flows, forms, and CTAs so engineering teams can prioritize by business impact
📦 Bulk triage + export filter by severity/effort (S/M/L), export as CSV, JSON, Markdown, or HTML for sprint planning
🔒 Privacy-first all DOM analysis runs locally in your browser; PII is auto-redacted before any AI call
Why now? The EU Accessibility Act enforcement started June 2025. ADA litigation in the US is at record highs. Accessibility is no longer optional but most developer tooling still treats it as an afterthought.
I'd love to hear from this community:
What's the biggest pain point in your current a11y workflow?
Are there specific WCAG checks or framework integrations you wish existed?
Happy to answer any technical questions about how the heuristics engine or AI remediation pipeline works.
Replies