Lumi vs Lighthouse
What Lighthouse accessibility audits are missing
Google Lighthouse includes an accessibility audit powered by a subset of axe-core rules. It's built into Chrome DevTools and useful for quick checks - but it's not an accessibility tool. It runs fewer rules than axe-core itself and doesn't test keyboard navigation.
What Lumi finds that Lighthouse misses
300+ rules vs ~60 - five engines instead of a single-engine subset
Keyboard interaction testing (focus traps, focus obscured, tab order)
64 custom checks that axe-core doesn't have
WCAG 2.2 checks (Focus Not Obscured, Accessible Authentication)
Multi-page crawling and continuous monitoring
Score tracking with regression alerts
CI/CD API with score threshold gates
Where Lighthouse falls short
Runs only a subset of axe-core rules - fewer checks than axe itself
Accessibility score can be misleading (100 doesn't mean compliant)
No keyboard interaction testing
No custom accessibility checks beyond axe-core subset
No monitoring, scan history, or regression alerts
Single page per audit