Accessibility is one of those things that almost every design team agrees is important and almost every design team treats as an afterthought. It gets added to the backlog, scheduled for “the next sprint,” and quietly deprioritized when timelines get tight. I’ve been guilty of this myself. But after spending time with users who rely on screen readers, switch controls, and keyboard navigation to use the products I’ve helped build, my perspective shifted permanently. Accessibility stopped being a compliance checkbox and became a fundamental quality signal — if someone can’t use what I designed, I haven’t finished designing it.
The good news is that accessible design and good design are almost always the same thing. High color contrast helps users in bright sunlight, not just those with low vision. Large tap targets help people on crowded trains, not just those with motor impairments. Clear error messages help anxious first-time users, not just those with cognitive differences. When you design for the edges, the middle takes care of itself. I’ve started running a simple accessibility check as part of every design review: keyboard-only navigation, 4.5:1 contrast ratio, descriptive link text, and a quick VoiceOver pass. It adds maybe twenty minutes and catches issues that would take ten times longer to fix after launch.
Alex Rivera 
Leave a comment