Apollo Editor
Windows 10 & 11 Buy now · $69.95
Design & SEO

Website Accessibility Basics: A Practical Checklist for Small Sites

A practical accessibility checklist for small websites: headings, alt text, color contrast, link text, forms, keyboard use and language settings.

Updated 5 minute read The Apollo Editor team

A basic website accessibility checklist covers a handful of things: a logical heading structure, alt text on images, enough color contrast, descriptive link text, labeled form fields, full keyboard access with a visible focus, and the page language set in the HTML. Getting these right makes a small site usable for far more people, including those using screen readers, keyboards or screen magnifiers. Most fixes take minutes and also help everyone else.

This guide explains each item on the checklist, how to test it yourself, and where the official standard comes in.

What accessibility means and which standard to follow

An accessible website is one that people with disabilities can perceive, understand, navigate and use. That includes people who are blind or have low vision, are deaf or hard of hearing, have motor impairments that make a mouse hard to use, or have cognitive differences.

The most widely used standard is the Web Content Accessibility Guidelines (WCAG) from the W3C. The current version is WCAG 2.2. Its success criteria come in three levels, A, AA and AAA, and level AA is the usual target for websites. You do not need to read the whole standard to make a big improvement. The checklist below covers the issues that come up most often on small sites.

The checklist

CheckWhat good looks like
Page language<html lang="en"> (or your language) on every page
Page titlesA unique, descriptive <title> on every page
HeadingsOne <h1>, then <h2> and <h3> in order, used for structure not looks
ImagesMeaningful alt text, or alt="" for decoration
Color contrastAt least 4.5 to 1 for normal text, 3 to 1 for large text
Color aloneInformation is never shown only by color
LinksLink text that makes sense out of context
FormsEvery field has a visible <label>; errors are explained in text
KeyboardEverything works with Tab, Shift+Tab, Enter and Space; focus is visible
MediaCaptions for video; transcripts for audio; no autoplaying sound
Zoom and mobileContent still works when zoomed to 200% and on a narrow phone screen

Structure: language, titles and headings

Set the language with the lang attribute on the <html> element. Screen readers use it to choose the right pronunciation. Without it, a page in Spanish might be read with English rules.

Give every page a clear title so people know where they are when they switch tabs or hear it announced. Then structure the content with real headings. Screen reader users often jump from heading to heading to find what they need, much like sighted people scan. Use one <h1> for the page's main topic, <h2> for sections and <h3> for subsections, without skipping levels. If you want text to look bigger, use CSS rather than picking a heading level for its size.

HTML landmark elements such as <header>, <nav>, <main> and <footer> also help assistive technology users move around the page quickly.

Images

Every <img> needs an alt attribute. Describe what the image communicates, and use an empty alt="" for decorative images so screen readers skip them. Our alt text guide has examples for photos, logos, buttons and charts.

Color contrast

Low contrast text, such as light gray on white, is hard to read for many people, especially on phones outdoors. WCAG level AA asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text. Large text means at least 18 point (about 24 CSS pixels), or 14 point bold (about 18.5 CSS pixels). Buttons, form field borders and icons that people need to see should reach at least 3 to 1 against their background. Free contrast checkers let you enter two colors and see the ratio.

Do not rely on color alone

If a form shows errors only by turning a field red, people who cannot distinguish red will miss it. Add text or an icon too. The same goes for links inside paragraphs: an underline helps them stand out from the surrounding text.

Link text

Links like "click here" or "read more" are meaningless when a screen reader lists all links on a page. Write "Read our returns policy" instead, and mention when a link opens a file or a new tab.

Interaction: forms and keyboard use

Forms

Every form field needs a label that is tied to it, so that screen readers announce what the field is for:

  • <label for="email">Email address</label>
  • <input type="email" id="email" name="email" autocomplete="email">

Placeholder text is not a substitute for a label, because it disappears when people start typing. Mark required fields in text, not just with color, and explain errors clearly next to the field.

Keyboard access

Many people navigate with a keyboard or a device that acts like one. Put your mouse aside and press Tab through your page. You should be able to reach every link, button and form field in a sensible order, and always see where you are. Use real <button> and <a> elements for things people click, because a styled <div> does not work with the keyboard by default. Do not remove the focus outline with CSS unless you replace it with a clearly visible style of your own.

How to test your site in 15 minutes

  1. Keyboard test: Tab through the home page and one inner page. Note anything you cannot reach or cannot see.
  2. Zoom test: zoom the browser to 200% and check that nothing overlaps or gets cut off.
  3. Heading check: look at the headings in your HTML and confirm they form a sensible outline.
  4. Image check: search your pages for <img and confirm each has an alt attribute.
  5. Contrast check: run your main text, link and button colors through a contrast checker.
  6. Screen reader try: Windows includes Narrator (press Windows logo key + Ctrl + Enter). Listen to a page for a minute.

Automated checkers in browsers can catch many technical problems, but not all. A quick manual pass like this finds the issues that matter most to real visitors.

The easier way: start from accessible building blocks in Apollo Editor

Many accessibility problems come from the HTML underneath the design. Apollo Editor lets you build pages visually while keeping that HTML clean and easy to check.

  • Start from one of 30 responsive templates, then add alt text to every image in the Image Properties dialog.
  • Set the page language and title in File > Page Properties.
  • Choose text and background colors in the CSS Style Designer, and check the layout at phone sizes in Preview mode.
  • Review headings, labels and attributes in Split or Code mode, with HTML validation that highlights errors.

Accessibility is ongoing work rather than a one-off task, so revisit this checklist when you add new pages. Related guides: how to make a contact form in HTML, how to make a website responsive and how to add links in HTML.

Frequently asked questions

What is WCAG?

The Web Content Accessibility Guidelines, published by the W3C, are the most widely used standard for making websites accessible.

What color contrast does text need?

WCAG level AA asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text.

Why does heading order matter?

Screen reader users often navigate by headings, so a logical order of h1, h2 and h3 makes a page much easier to use.

Get three guides like this every month, plus software update notices.Subscribe →