Articles
What we're seeing
What Esther measures across the websites it assesses, published as it happens. Findings from the data, a reference page for each WCAG criterion, a monthly roundup, and responses when a regulator acts.
All: 16 articles
Latest ·
Who Can Answer for Your Website's Accessibility?
Two barriers appeared on 91% of government websites over the past six months. Whether anyone in an organization can say if its own site has them, and since when, is a question of oversight more than code.
Rick Hensbergen · 4 min read
- Records
- Government
- Oversight
- Reference
Why Does the Tab Key Jump Around a Web Page?
When the keyboard highlight jumps from the menu to the footer and back, people who move through a page without a mouse lose their place. What WCAG's Focus Order criterion asks, who it affects, and why the fix is usually small.
Ash Harris · 4 min read
- Reference
- Keyboard
- WCAG 2.4.3
- Response
Does Missouri Require Notice Before an ADA Website Lawsuit?
Missouri's new law sets no notice a plaintiff must send before suing over website accessibility. What it does set: a way to ask a court to rule a suit abusive, and 90 days in which a fix can count, if the court finds it held.
Rick Hensbergen · 5 min read
- Lawsuits
- State law
- Missouri
- Records
- Findings
What Do Website Accessibility Lawsuits Name, and What Do They Leave Out?
We read recent website accessibility complaints from three plaintiffs who each filed several. Most name pictures and buttons a screen reader can't describe. None names faint text.
Rick Hensbergen · 4 min read
- Lawsuits
- Screen readers
- Images
- Contrast
- Response
Is WCAG 3 a Standard Yet?
W3C updated its WCAG 3 draft on September 10, 2026, and calls it an incomplete draft that will change. Most of the rules websites answer to today are based on WCAG 2.
Ash Harris · 4 min read
- WCAG
- Standards
- Records
- Response
Sued Again: Why Settling an Accessibility Suit Doesn't Fix the Website
One shoe brand's website was sued over accessibility in 2022, 2024, and 2026, each time by someone new. What the court record shows about why settling one case doesn't end the exposure.
Ash Harris · 5 min read
- Lawsuits
- Screen readers
- Retail
- Records
- Briefing
Does a Clean Accessibility Report Mean a Clean Website?
Esther found button text too faint to read, at a color contrast of 3.94 to 1 where the standard is 4.5 to 1. The automated report on the same pages showed none of it.
Rick Hensbergen · 3 min read
- Contrast
- Screen readers
- Records
- Briefing
What We Told NIST About Proving a Vulnerability, and Why
Our filing to NIST argues that a security record should carry proof, so automation follows the evidence and a named person signs off wherever the consequence is high.
Rick Hensbergen · 4 min read
- Security
- Records
- Evidence
- NIST
- Response
Unable to Send Money: The Accessibility Suit Over Chase's Website
A man who is legally blind says he could not send money on Chase's website with his screen reader. What the court record shows about where the suit started, what it asks for, and what happens next.
Rick Hensbergen · 5 min read
- Lawsuits
- Screen readers
- Banking
- Records
- Briefing
How Quickly Can Website Accessibility Barriers Come Down?
One web service's signed-in screens, assessed after every round of changes. In three days the list Esther found fell to about a seventh of where it started, with none at Level A.
Rick Hensbergen · 4 min read
- Templates
- Keyboard access
- Text spacing
- Records
If any of this strikes a nerve, we should talk.
Thirty minutes. Your situation, and where to begin.
