You’re Probably Not Testing Accessibility the Way Users Experience It
📰 Dev.to · R3TICULAR
Most frontend developers today use tools like Axe, WAVE, or Lighthouse to test accessibility. And...
Full Article
Title: You’re Probably Not Testing Accessibility the Way Users Experience It
URL Source: https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em
Published Time: 2026-04-13T22:41:48Z
Markdown Content:
# You’re Probably Not Testing Accessibility the Way Users Experience It - DEV Community
[Skip to content](https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em#main-content)
[](https://dev.to/)
[Powered by Algolia](https://www.algolia.com/developers/?utm_source=devto&utm_medium=referral)
[Log in](https://dev.to/enter?signup_subforem=1)[Create account](https://dev.to/enter?signup_subforem=1&state=new-user)
## DEV Community
0 Add reaction
0 Like 0 Unicorn 0 Exploding Head 0 Raised Hands 0 Fire
0 Jump to Comments 0 Save Boost
Copy link
Copied to Clipboard
[Share to X](https://twitter.com/intent/tweet?text=%22You%E2%80%99re%20Probably%20Not%20Testing%20Accessibility%20the%20Way%20Users%20Experience%20It%22%20by%20R3TICULAR%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)[Share to LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em&title=You%E2%80%99re%20Probably%20Not%20Testing%20Accessibility%20the%20Way%20Users%20Experience%20It&summary=Most%20frontend%20developers%20today%20use%20tools%20like%20Axe%2C%20WAVE%2C%20or%20Lighthouse%20to%20test%20accessibility.%20%20And...&source=DEV%20Community)[Share to Facebook](https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)[Share to Mastodon](https://s2f.kytta.dev/?text=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)
[Share Post via...](https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em#)[Report Abuse](https://dev.to/report-abuse)
[](https://dev.to/r3ticular)
[R3TICULAR](https://dev.to/r3ticular)
Posted on Apr 13
# You’re Probably Not Testing Accessibility the Way Users Experience It
[#a11y](https://dev.to/t/a11y)[#webdev](https://dev.to/t/webdev)[#api](https://dev.to/t/api)
Most frontend developers today use tools like Axe, WAVE, or Lighthouse to test accessibility.
And that’s a good start.
But there’s a gap that these tools don’t really cover:
They don’t tell you what a screen reader user actually hears.
The Problem: Accessibility ≠ Announcement
Let’s take a simple example:
From a rule-based perspective, this passes:
-It has an accessible name
-It uses a semantic element
But what does a screen reader actually announce?
NVDA: “Submit Payment, button”
URL Source: https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em
Published Time: 2026-04-13T22:41:48Z
Markdown Content:
# You’re Probably Not Testing Accessibility the Way Users Experience It - DEV Community
[Skip to content](https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em#main-content)
[](https://dev.to/)
[Powered by Algolia](https://www.algolia.com/developers/?utm_source=devto&utm_medium=referral)
[Log in](https://dev.to/enter?signup_subforem=1)[Create account](https://dev.to/enter?signup_subforem=1&state=new-user)
## DEV Community
0 Add reaction
0 Like 0 Unicorn 0 Exploding Head 0 Raised Hands 0 Fire
0 Jump to Comments 0 Save Boost
Copy link
Copied to Clipboard
[Share to X](https://twitter.com/intent/tweet?text=%22You%E2%80%99re%20Probably%20Not%20Testing%20Accessibility%20the%20Way%20Users%20Experience%20It%22%20by%20R3TICULAR%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)[Share to LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em&title=You%E2%80%99re%20Probably%20Not%20Testing%20Accessibility%20the%20Way%20Users%20Experience%20It&summary=Most%20frontend%20developers%20today%20use%20tools%20like%20Axe%2C%20WAVE%2C%20or%20Lighthouse%20to%20test%20accessibility.%20%20And...&source=DEV%20Community)[Share to Facebook](https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)[Share to Mastodon](https://s2f.kytta.dev/?text=https%3A%2F%2Fdev.to%2Fr3ticular%2Fyoure-probably-not-testing-accessibility-the-way-users-experience-it-46em)
[Share Post via...](https://dev.to/r3ticular/youre-probably-not-testing-accessibility-the-way-users-experience-it-46em#)[Report Abuse](https://dev.to/report-abuse)
[](https://dev.to/r3ticular)
[R3TICULAR](https://dev.to/r3ticular)
Posted on Apr 13
# You’re Probably Not Testing Accessibility the Way Users Experience It
[#a11y](https://dev.to/t/a11y)[#webdev](https://dev.to/t/webdev)[#api](https://dev.to/t/api)
Most frontend developers today use tools like Axe, WAVE, or Lighthouse to test accessibility.
And that’s a good start.
But there’s a gap that these tools don’t really cover:
They don’t tell you what a screen reader user actually hears.
The Problem: Accessibility ≠ Announcement
Let’s take a simple example:
From a rule-based perspective, this passes:
-It has an accessible name
-It uses a semantic element
But what does a screen reader actually announce?
NVDA: “Submit Payment, button”
DeepCamp AI