Accessibility Quick-Check

Ship WCAG 2.2 & EAA-ready screens

5 topics · 20 checks 0%

Perceivable

Text alternatives Every meaningful image, icon and chart has an alt that conveys its purpose. Decorative images are marked empty so screen readers skip them.
Colour contrast Body text meets at least 4.5:1 against its background, large text 3:1. Buttons, inputs and icons meet 3:1 for their non-text parts.
Colour isn't the only signal Errors, links and states carry a second cue beyond colour: text, an icon or an underline. Nothing is lost in greyscale.
Captions & transcripts Video has captions and audio has a transcript, so the content works without sound and without sight.

Full keyboard access Every action works with the keyboard alone, in a logical order, with no traps. Try the whole flow without touching the mouse.
Visible focus The focused element is always clearly outlined. WCAG 2.2 asks that the focus indicator is not hidden behind sticky headers or other content.
Target size Interactive targets are at least 24 by 24 CSS pixels, or have enough spacing around them. Small, crowded controls fail people with motor difficulties.
No motion traps Nothing flashes more than three times a second, and auto-playing motion can be paused. Respect the reduced-motion setting.
Enough time Time limits can be extended or turned off, so people who need longer aren't cut off mid-task.

Labels on every field Each input has a visible, programmatic label. Placeholder text is not a substitute; it disappears the moment someone types.
Clear, specific errors Error messages name the field and say how to fix it. The field is identified in text, not by colour alone.
Don't make people re-enter WCAG 2.2 asks that information a user already gave earlier in a process is carried forward or selectable, not re-typed from memory.
Plain, consistent language Navigation and component labels stay consistent across the product, and copy is written for a general reading level.

Semantic structure Headings, lists, landmarks and buttons use the right elements. A screen reader should understand the page from its markup, not its looks.
Name, role, value Custom components expose their name, role and state to assistive tech. If you build a toggle, it must announce whether it is on or off.
Test with a screen reader Run the core flow with a real screen reader and with the page zoomed to 200 percent. Automated checkers catch roughly a third of issues.

Are you in scope? The European Accessibility Act has applied to many consumer products and services since 28 June 2025. E-commerce, banking, transport and communications aimed at EU consumers are common triggers.
Know your baseline WCAG 2.1 level AA is the practical target most EU conformance maps to. Meeting WCAG 2.2 AA keeps you ahead as guidance updates.
Accessibility statement Publish how your product meets the requirements, known gaps, and how people can report a barrier or ask for help.
Build it into the process Bake accessibility acceptance criteria into design and QA. Retrofitting after launch costs far more than designing it in from the start.

Progress auto-saves in this browser — no account, nothing leaves your device.