You can treat formulaire accessible as a checkbox, or as a design decision. The first path is fast and ineffective; the second takes an hour of thought and lasts for years.
Test with more than a validator
Automated tools catch at best a third of problems. They will never tell you a label is incomprehensible or a journey is absurd.
Ten minutes of keyboard navigation, then ten with a screen reader, teach more than a fifty-page report.
The five most profitable fixes
Sufficient contrast, explicit link labels, associated form labels, a coherent heading hierarchy and a visible focus: these five cover the majority of real obstacles.
None requires a redesign, and all can be checked in under an hour on a mid-sized site.
The real cost of doing nothing
An untreated technical problem does not stay stable: it spreads. Every new piece published on a faulty structure inherits the defect, and remediation cost grows with volume.
That is why fixing a structural flaw on a hundred-page site beats waiting until you have a thousand. The work is the same; the cleanup is not.
Check before moving on
- Automate every repetitive check
- Document the decision, not just the action
- Schedule a review in six months
- Remove before adding
Accessibility is not an end-of-project option
Handled at design time, it costs almost nothing. Added after launch, it forces reworking entire components, sometimes a whole design system.
The right question is not 'how do we make this site accessible' but 'what in our defaults systematically produces inaccessible output'.
A benefit beyond the intended audience
Captions also help on a noisy train, high contrast helps in bright sunlight, keyboard navigation speeds up expert users.
That is why it is more accurate to speak of usage quality than regulatory compliance.
Read next
Where to start
If you take only one action from this article, take the one touching the largest number of pages at once: the effort-to-impact ratio is almost always best there. The rest follows more easily.
