Blog / How the internet works /

Website accessibility basics

Try something. Put your mouse aside and navigate your own website using only the Tab key. Can you reach the menu? See where you are? Open the main button? If you got stuck, you’ve just felt what many visitors experience every day.

Web accessibility means building sites that people can use whatever their abilities or situation: someone who is blind, someone with low vision, someone who can’t use a mouse, someone who is deaf, someone with a learning difference, and also someone squinting at a phone in the sun, or using one hand because the other holds a child.

You don’t need to be an expert. A few basics fix most of the problems.

Why it matters, in plain terms

  • More people can use your site and buy from you. A large share of the world’s population lives with some form of disability, and many more have temporary or situational limits.
  • It’s often a legal expectation. Rules differ by country, but laws and standards on digital accessibility keep expanding. The European Accessibility Act, for example, began applying to many digital products and services in June 2025.
  • It overlaps with SEO and general quality. Clear headings, descriptive links and alt text help search engines too. I covered the overlap in accessibility and SEO: where they overlap.

The standard most people use is WCAG (the Web Content Accessibility Guidelines), now at version 2.2. It is organised around four ideas: content must be perceivable, operable, understandable and robust.

The seven basics

1. Headings that make sense

Use headings to describe structure, not to make text big. One main heading (H1) per page, then H2s for sections and H3s for sub-sections, in order. Screen reader users often jump from heading to heading to scan a page, just as sighted users skim.

Test: read only your headings. Do they outline the page?

2. Alt text for images that carry meaning

Alt text is a short description of an image for people who can’t see it. Write what the image tells the reader, not “image of…”.

  • Informative image: describe the point (“Graph showing sales rising each month”).
  • Decorative image: leave the alt empty so screen readers skip it.
  • Image with text in it: the alt text should include that text, or better, put the text on the page.

I went deeper in reviewing WordPress media alt text.

3. Colour contrast

Text needs enough contrast against its background. WCAG asks for at least 4.5:1 for normal text and 3:1 for large text. Pale grey on white looks elegant and is unreadable for many people.

Also, never use colour alone to carry meaning. “Fields in red are required” fails for colour-blind users; add a label or icon.

Test: use a contrast checker in your browser developer tools or a free online tool, and check buttons and form hints, not just body text.

4. Keyboard access

Everything you can do with a mouse should be possible with a keyboard: menus, buttons, forms, pop-ups and carousels. You should always see where the focus is (a visible outline), and focus shouldn’t get trapped in a modal.

Test: unplug the mouse for five minutes and use Tab, Shift+Tab, Enter and Space.

“Click here” and “Read more” mean nothing out of context, and screen readers can list all the links on a page. Use link text that says where it goes: “Read the returns policy”.

Make buttons and tap targets big enough to hit comfortably on a phone. I’ve gone through this for builders in planning accessible link and button labels in Framer.

6. Forms that explain themselves

Every field needs a visible label (not just placeholder text that disappears). Error messages should say what went wrong and how to fix it, next to the field, and not only in colour. Group related fields and mark required ones clearly.

Forms are where accessibility and money meet: a checkout that confuses a screen reader user loses a sale.

7. Media with alternatives

Videos need captions. Audio needs a transcript. Auto-playing media with sound should be avoided, or easy to stop. Captions help far more people than expected: anyone in a noisy place or without headphones.

Beyond the seven

  • Text resizing. The page should still work when someone enlarges text or zooms.
  • Respect motion preferences. Heavy animation can cause discomfort; honour the “reduce motion” setting.
  • Set the page language in the HTML, so screen readers pronounce it correctly.
  • Meaningful page titles. Each page needs a distinct one.
  • Don’t rely on overlays. One-click “accessibility widgets” that promise to fix everything usually don’t, and they can interfere with the assistive tools people already use.

A 15-minute test you can run today

  1. Keyboard-only walk through your homepage and one form.
  2. Run an automated checker (Lighthouse’s accessibility audit is built into Chrome). It catches only part of the issues, but it’s a start.
  3. Zoom to 200% and see what breaks.
  4. Turn on a screen reader briefly (VoiceOver on Apple devices, TalkBack on Android, NVDA on Windows) and listen to one page.
  5. Read the headings and links out of context.

Automated tools find roughly the easy half. The rest needs a human looking and listening, which is why that Tab-key test matters.

Common myths

  • “It’s expensive.” Building it in from the start costs little. Retrofitting everything later costs more.
  • “It makes sites ugly.” Good accessible sites look good. Contrast and clarity are design virtues.
  • “Only a small group benefits.” Captions, contrast, clear forms and keyboard support help almost everyone at some point.
  • “A plugin will fix it.” Tools help you find problems; fixing them is a design and content job.

Where to go next

For a fuller list on a small business site, see an accessibility checklist for small business websites. If you’re thinking about the broader tech picture, I wrote about phone accessibility settings everyone should know.

Key takeaways

  • Accessibility means more people can use your site, and it supports SEO and conversions.
  • Start with headings, alt text, contrast, keyboard access, links, forms and media.
  • Test by tabbing through the page, zooming and listening to a screen reader.
  • Automated checkers catch only part of the problem.

Take five minutes now: put the mouse down, press Tab on your homepage and see how far you get. What you find there is your first fix.