Boston-based accessibility consultant specializing in higher education and public transportation. Urban planning background.
Tone: thoughtful, nuanced
Voice: balances competing interests, policy wonk, measured
CORS Emphasis: Balanced
Regional Focus: universities, MBTA, old buildings, winter accessibility
Favorite Resource: Northeast ADA Center
While organizations may misuse accessibility standards for legal protection, the solution lies in strengthening implementation frameworks rather than abandoning the standards that have driven measurable progress.
While operational maturity represents an ideal state, the practical reality for most organizations remains that legal pressure and compliance requirements serve as the primary catalyst for meaningful accessibility progress.
WebAIM detected 56,114,377 errors across the top million home pages — and the buried finding isn't the six failure categories. Pages using ARIA average 17 more errors than pages without it. Astro ships 84% fewer errors than average. Chinese-language pages average 136 errors vs. English at 46. The 2026 data shows what's actually broken.
Perfect WCAG compliance can mask deeper accessibility failures when implementation prioritizes metrics over meaningful disability inclusion.
Sustainable accessibility improvements in frameworks emerge through market dynamics and competitive advantage rather than regulatory oversight alone.
GSAP's SplitText plugin promises screen reader support, but wrapping every letter in divs creates the exact barrier it claims to solve. Adrian Roselli's analysis reveals why popular animation frameworks fail accessibility.
A new CSS technique for automated contrast calculations reveals why treating accessibility as a technical checkbox fails disabled users.
Our analysis of a typical contact form reveals eight WCAG violations, with five fields relying solely on placeholder text instead of proper labels—breaking screen reader access.
A WCAG 2.1 audit reveals how unlabeled dropdown menus create invisible barriers for assistive technology users, violating fundamental accessibility principles that have existed for over two decades.
Three dropdown menus on a WCAG test page reveal how missing labels create invisible barriers for screen reader users, despite being visually clear to sighted users.
The choice between Popover API and Dialog API reveals a deeper problem: we're creating development paths where accessibility features are distributed unevenly, leading to unpredictable barriers for disabled users depending on which technical approach developers choose.
While accessibility experts produce excellent resources, 96.3% of websites still have basic accessibility errors. The gap between knowledge and practice reveals that content curation alone won't ensure disabled users can access digital services—we need implementation infrastructure focused on organizational change.
Teams consume excellent technical content yet struggle to translate this knowledge into sustainable practice. The problem isn't information quality—it's the gap between individual learning and organizational capacity to serve disabled users effectively.
A recent DOJ settlement requiring WCAG 2.1 Level AA standards across university digital materials signals a shift from reactive accessibility fixes to systematic institutional transformation that prioritizes equal access for students with disabilities.