Technical
Frontend Skill I Am Finally Taking Seriously: Accessibility
I have shipped accessible-enough frontends for years. Not accessible. Accessible-enough. In 2026 I am taking it seriously for a business reason: the clients I want demand it and the regulators in some markets are catching up. Here is the learning plan I put together and the gaps I found in my own practice.
What I Was Missing
- Keyboard navigation tested beyond tab order
- Screen reader checks on actual screen readers, not linters
- Color contrast on every state, not just default
- Focus management in modal and dialog flows
- Announced updates for async UI changes
Each of these looks small on its own. Taken together, they represent the difference between an interface that technically passes axe and one that real users with real assistive technology can actually use.
The Learning Path
- WCAG 2.2 AA as the baseline standard
- The WAI-ARIA Authoring Practices for component patterns
- VoiceOver and NVDA as my testing tools
- axe-core in CI for automated regressions
- Manual keyboard-only testing once a week on my own projects
The manual testing is the part most developers skip. I am adding it to my Friday ritual.
Why It Is Now a Sales Lever
Enterprise prospects ask about accessibility on every call. Public sector contracts require it. If I am the consultant who can document compliance by default, I win work that other consultants cannot even bid on. The ROI on accessibility competence is higher in 2026 than any other frontend skill I could add.
The Test I Run Now
Close laptop lid.
Connect external keyboard.
Reopen laptop.
Navigate the whole site without touching the trackpad.If you cannot, you have a problem. I ran this on five of my past client projects last week and three failed. Fixing them is on my backlog for Q1.
What Changes in My Component Library
Every shared component gets accessibility tests. Every story in Storybook gets run through axe. The cost is small. The positioning upgrade is significant. The WAI-ARIA Authoring Practices are the canonical reference.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read