Accessible by default: five checks before every pull request
Accessibility is not a final polish step. Five quick checks catch most problems before they ship, and they take less time than you think.

Accessibility often gets treated as a final polish step, something to look at after launch if there is time. There rarely is. The good news is that most accessibility bugs are small and easy to fix, as long as you catch them early.
We ask every trainee to run five quick checks before opening a pull request. Together they take a few minutes, and they catch the large majority of problems.
1. Can you reach everything with the keyboard?
Put the mouse away and press Tab. Every link, button and field should be reachable, in a sensible order, with a visible focus ring.
2. Does every image have a sensible alt text?
Describe what the image means in context. Decorative images get an empty alt so screen readers skip them.
<img src="/team.jpg" alt="Trainees reviewing code together" /><img src="/divider.svg" alt="" />3. Is the contrast high enough?
Light grey text on white looks elegant and is unreadable for many people. Check text against its background, especially on coloured sections.
4. Do form fields have labels?
A placeholder is not a label: it disappears as soon as someone types. Every field needs a real label, even if it is visually subtle.
<label for="email">Email</label><input id="email" type="email" autocomplete="email" />5. Does the page still work at 200% zoom?
Zoom in and use the page. Text should wrap, nothing should overlap, and you shouldn't need to scroll sideways to read a sentence.
Accessible sites are better sites for everyone, not just for some.
We review these five on every pull request in the Frontend path. After a few weeks, nobody needs the list any more: the checks have become habits.






