WCAG explained without the jargon — the fixes that resolve most real problems, how to test without specialist tools, and where the legal obligations sit.
Accessibility is often treated as a compliance checkbox added at the end. Done that way it is expensive and rarely works. Designed in from the start it costs very little and makes the site better for everyone — accessible sites are typically faster, clearer and easier to use on a phone.
WCAG, briefly
The Web Content Accessibility Guidelines are the standard almost every regulation points at. Three conformance levels: A (minimum), AA (the practical target, and what most laws reference), and AAA (rarely required in full).
The guidelines organise around four principles — content must be perceivable, operable, understandable and robust. That framing is more useful than the numbered criteria when you are making decisions.
The fixes that resolve most real problems
Colour contrast
Body text needs a contrast ratio of at least 4.5:1 against its background; large text 3:1. Light grey on white is the most common failure on well-designed sites, and it affects far more people than most teams assume.
Everything reachable by keyboard
Tab through your site without touching the mouse. You must be able to reach every link, button and form field, and see where you are. Removing focus outlines because they look untidy is the most damaging small decision in web design.
Real alt text
Describe what the image conveys, not what it depicts. A photo of a team at a whiteboard is not "people in an office" — if it illustrates a workshop, say so. Decorative images take an empty alt="" so screen readers skip them.
Labelled form fields
Every input needs a real label, not just placeholder text. Placeholders disappear on focus and are not reliably announced. Error messages must say what is wrong and how to fix it.
Headings in order
One h1 per page, then h2, then h3, without skipping levels. Screen reader users navigate by heading; a broken hierarchy is like a table of contents with the chapters shuffled.
Test it yourself in ten minutes: tab through a page start to finish; zoom the browser to 200% and check nothing is lost; turn on your operating system's built-in screen reader and try to complete your main call to action.
Where automated tools stop
Automated checkers catch perhaps a third of real issues — contrast, missing alt attributes, missing labels. They cannot tell you whether alt text is meaningful, whether the tab order makes sense, or whether an error message is comprehensible. Run them, then do the manual pass anyway.
The legal position, in short
Obligations vary by jurisdiction and sector. Public sector bodies are covered almost everywhere. Private-sector obligations are broader than most businesses assume and are tightening, particularly in the EU and for anyone selling to public bodies. If your organisation has a legal team, this is a question worth asking them early rather than after a complaint.
Build it in, do not bolt it on
Put accessibility in the acceptance criteria of any new build, alongside performance targets. Retrofitting a finished site costs several times more than designing it in, and the result is always worse.
Frequently asked questions
What accessibility level should I aim for?
WCAG 2.2 Level AA. It is what almost every regulation references and it is achievable without compromising design. AAA in full is rarely required and sometimes impractical.
Do accessibility overlay widgets work?
Not as a substitute for fixing the underlying site. They do not resolve most real barriers, disability advocacy groups broadly oppose them, and their presence has not prevented legal claims. Fix the markup instead.
Does accessibility help SEO?
Substantially overlapping. Semantic headings, alt text, descriptive links and clear structure help both. They are not the same discipline, but work on one usually improves the other.
