Back to blog

Web Accessibility: A Checklist You Can Work Through in an Afternoon

Most accessibility failures come from a short list of repeated mistakes. Find them with simple tools and fix them with small changes.

Person using a screen reader to navigate a website

Accessibility is usually imagined as a huge, intimidating project. In practice most failures on most sites come from a short and very repetitive list. Close that list and the experience genuinely improves for a large group of users.

The recurring problems

  • Low contrast text. Light grey on white looks elegant until someone reads it in sunlight or with tired eyes. Body text needs a contrast ratio of at least 4.5:1.
  • Missing alt text. An image without alt is nothing at all to a screen reader.
  • Unlabelled form fields. A placeholder is not a label; it disappears the moment typing starts.
  • Buttons that are actually divs. Not focusable, not activated by Enter, invisible to assistive technology.
  • Removed focus rings. outline: none with no replacement makes a site unusable by keyboard.
  • Broken heading order. Jumping from h1 to h4 destroys the document outline people navigate by.
Checking colour contrast and text legibility in an interface
Contrast and labelling account for most automatically detectable failures.

Testing without expensive tools

  1. Put the mouse away. Complete your signup or checkout flow using only Tab and Enter. Every place you get stuck is a bug.
  2. Zoom to 200%. The page must stay usable and text must not be clipped.
  3. Turn on your operating system's screen reader. Ten minutes listening to your homepage teaches more than ten automated reports.

Automated checkers catch roughly a third of issues. Take that third for free, but do not mistake it for completion.

ARIA: less is more

The first rule of ARIA is not to use ARIA. If a native HTML element exists — button, nav, label, dialog — use it and get correct behaviour for free. ARIA is for the cases with no native equivalent, and incorrect ARIA is worse than none.

A note on internationalized layouts

If your site also serves right-to-left languages, set direction with dir on the root element rather than with bespoke stylesheets, and use logical CSS properties such as margin-inline-start instead of margin-left so one stylesheet works in both directions. Wrap embedded Latin text and code with explicit direction so it does not scramble inside a sentence.

Why it pays off

Beyond the ethical case and the tightening legal requirements in several markets, nearly all of these changes make the site better for everyone: higher contrast, clearer labels, a working keyboard path, clean structure. That is also exactly what search engines and language models parse most reliably.

Web Accessibility: A Checklist You Can Work Through in an Afternoon — 1Web Accessibility: A Checklist You Can Work Through in an Afternoon — 2Web Accessibility: A Checklist You Can Work Through in an Afternoon — 3
Written by

Hesam Ziaee, a web developer and programmer who builds fast, user-friendly websites with Vue.js, Quasar and Node.js.