WCAG baselines

A few measurable rules cover most accessibility wins.

How to apply it

Hit 4.5:1 text contrast, 44pt targets, labelled inputs, and visible focus.

WCAG baselines in practice: a concrete example

Four checks that catch most of it

You don't need the whole WCAG spec memorised to ship an accessible product; a short, measurable baseline catches the majority of real-world failures. Hit 4.5:1 text contrast, 44pt touch targets, a label on every input, and a visible focus ring on every interactive element, and you have cleared the issues automated scanners and real users trip over most. It turns “is this accessible?” from an overwhelming question into a four-item pre-ship checklist.

Common WCAG baselines mistakes

Treating accessibility as a final audit instead of a handful of habits applied as you build, so violations pile up and the fix feels huge.
Trusting an automated scanner alone; it catches contrast and missing labels but not keyboard traps or a nonsensical reading order.
Shipping controls with no visible focus state, which silently locks out everyone navigating by keyboard.

When WCAG baselines doesn't apply

The baseline is a floor, not full conformance. Products with legal obligations, public-sector work, or users who depend on assistive tech need the complete WCAG AA (or AAA) pass, including keyboard operability, screen-reader semantics, and reduced-motion support. Treat these four as the minimum that keeps obvious barriers out, never as proof an interface is fully accessible.

Practise it on a real challenge

Match each accessibility need to its rule

Accessibility feels fuzzy until you anchor it to a few measurable rules.