We've started treating WCAG 2.1 compliance as a baseline requirement on our projects rather than an optional add-on, for a reason beyond good ethics: it's also good practice for everyone. Captions help someone in a noisy office as much as someone who is deaf. A logical heading structure helps a sighted user scanning the page as much as it helps a screen reader. Accessibility work mostly turns out to be quality work with a more specific name.

Start with semantic HTML

The single highest-leverage habit is using elements for what they actually mean, not just how they happen to look:

<!-- Bad: a div pretending to be a button -->
<div class="btn" onclick="submit()">Submit</div>

<!-- Good: an actual button, focusable and keyboard-operable for free -->
<button type="submit">Submit</button>

A real <button> is keyboard-focusable, announced correctly by every screen reader, and triggerable with the space bar or Enter key - all without a single line of extra JavaScript. A styled <div> gives up every one of those for free behaviours and has to reimplement them by hand.

An eye icon inside a card, with a row of contrast bars beneath it
Contrast, structure and keyboard access - the three checks we run first.

Colour contrast is measurable, not subjective

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal body text against its background, and 3:1 for large text. This is a specific number you can test, not a design opinion:

/* Fails AA on a light background */
color: #999; background: #fff; /* ~2.8:1 */

/* Passes AA */
color: #595959; background: #fff; /* ~7:1 */

Keyboard access, not just mouse access

Tab through your own site before shipping it. Every interactive element needs a visible focus state and a logical tab order - and nothing should ever set outline: none without providing a clearly visible replacement:

a:focus, button:focus {
  outline: 2px solid #1c6e63;
  outline-offset: 2px;
}

Alt text describes purpose, not just contents

<!-- The image is decorative - hide it from assistive tech -->
<img src="divider.svg" alt="">

<!-- The image conveys information - describe what it conveys -->
<img src="chart-q3-sales.png" alt="Q3 sales rose 18% over Q2, driven mainly by mobile">

Accessible isn't a separate version of a site. It's what "finished" was always supposed to mean.

None of this requires exotic tooling. A keyboard, a contrast checker, and the discipline to use HTML elements for what they mean will catch the large majority of issues before a dedicated audit ever needs to happen.

Four principles, easier to remember than the checklist

WCAG organizes around POUR: content must be Perceivable, Operable, Understandable, and Robust. Every specific success criterion - contrast ratios, keyboard operability, predictable navigation - maps back to one of those four, which makes POUR a genuinely useful mental checklist when reviewing a design that predates any formal audit.

/* WCAG AA minimum contrast for normal text */
/* 4.5:1 for text under 18px, 3:1 for larger/bold text */

Level A, AA, and AAA are a ladder, not a checklist to complete in order

Level AA is the realistic, widely-adopted target for most sites and the standard referenced in most accessibility legislation; AAA includes criteria (like the strictest contrast ratios) that are genuinely difficult to meet for a full design system without significant visual compromise. Aiming for AA across the whole site produces a far better real-world outcome than aiming for AAA on a handful of pages and leaving the rest untested.