# Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation

DevFeed: [Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation](<https://devfeed.tech/articles/llms-are-proving-that-it-is-impossible-to-automate-away-the-human-experience-33274.md>)

Original publisher: [Read original article](<https://8thlight.com/insights/llms-proving-impossible-automate-away-human-experience>)

Author: Celeste Aronow

Published: 2026-04-15T13:44:00Z

Content type: opinion

Language: en

Sources: [8th Light](<https://devfeed.tech/sources/8th-light.md>), [8th Light Insights](<https://devfeed.tech/sources/8th-light-insights.md>)

Topics: [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai-and-emerging-tech](<https://devfeed.tech/tags/ai-and-emerging-tech.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [llms](<https://devfeed.tech/tags/llms.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

The article argues that automated accessibility scanners and LLM-assisted auditing can identify many concrete issues and expand teams' coverage, but they cannot fully assess what people with disabilities experience when using a screen reader. It also warns that scan output can include false violations and requires human judgment and accessibility expertise.

## Source excerpt

The Gap is Real If your accessibility process ends with a passing scan, your users with disabilities are likely encountering barriers you do not know about. Automated tools are useful. LLM-assisted auditing has raised the ceiling. Neither closes the gap between what a tool can verify and what a person actually experiences when navigating with a screen reader. The gap is real, it is measurable, and it has organizational consequences. I have spent years running every category of automated accessibility tool the industry has produced: rule-based scanners like axe-core and WAVE, visual analyzers like Lighthouse, browser extensions with built-in screen reader simulations. When LLMs entered the picture, the promise was compelling. Tools that could finally understand context, interpret user flows, and reason about accessibility the way a human specialist does. I wanted that to be true. It isn't. What Automation Does Well Let me be fair to the tools. Automated accessibility scanners like axe-core, Lighthouse, and WAVE are genuinely good at what they do. They catch heading hierarchy violations quickly and reliably. They flag color contrast failures with precision. They identify missing alt attributes on images in many cases. These are real wins. If you have run these tools on your product, you have addressed real issues, and the engineers who did that work should feel good about it. Automated tooling is a force multiplier. It speeds up the work and amplifies how much ground a team can cover. The problem is not what these tools do. It is what they cannot do, and what organizations assume they have done. What Automation Invents The same tools I praised above (SilkTide, axe-core, Lighthouse, and WAVE) are genuinely valuable parts of a real accessibility workflow. They speed up discovery, give teams a shared vocabulary, and help non-specialists see problems that would otherwise be invisible. They also generate a lot of output. A single scan on a moderately complex page can retur