Or: How to spot the problem before someone else has to report it
You don’t need to be an expert – or use a screen reader – to notice when something feels off. In fact, most accessibility issues aren’t hidden behind complex code. They’re sitting right there in the open, if you know what to look for.
And more often than not, your gut already knows.
Accessibility starts with friction
If something feels harder than it should be, it probably is.
If you’re not sure what to click, where to look, or how to go back – you’re not alone.
That moment of hesitation? That’s a clue.
Your users will feel it too. And for some of them, it’s more than just annoying – it’s a brick wall.
Think like a human, not a validator
You don’t need to memorize every guideline to start spotting issues.
You just need to ask the right questions:
- Would this still make sense if I couldn’t see it?
- Could I recover if I clicked the wrong thing?
- Is there enough breathing room to read this comfortably?
- Would my mum or my kid or my stressed-out coworker know what to do next?
- If I left and came back later, would I still be able to find my place?
These aren’t trick questions. They’re gut checks. And the more you ask them, the better your instincts get.
Empathy isn’t optional – it’s a design skill
You don’t have to wait for an audit to know something’s broken.
You just have to care enough to notice.
That invisible label? That auto-playing video with no pause button? That form error hiding offscreen?
If you’ve ever felt a little lost, a little frustrated, a little unsure – then you already understand the problem.
The next step is doing something about it.