Web Accessibility Checklist: Make Your Website Usable for Everyone

Most website owners judge their site by how it looks to them. Accessibility is about everyone else: the customer who enlarges the text to read it, the visitor who navigates by keyboard because a mouse is hard to use, the person whose screen reader speaks the page aloud. When a site shuts these people out, it doesn't throw an error. It just quietly loses them.

The takeaway up front: web accessibility is not a special feature or a box-ticking chore — it's a set of concrete, mostly one-time fixes that make your site usable for more people, easier to find in search, and safer legally. You rarely need to rebuild anything. This checklist covers what to check, why each item matters, and how to test your own site without buying special software.

What web accessibility actually means

Web accessibility means building your site so people with disabilities — visual, motor, hearing, cognitive — can perceive, understand, and use it. That includes permanent disabilities and situational ones: bright sunlight on a phone screen, a broken arm, a noisy room where a video needs captions.

The recognized standard is the Web Content Accessibility Guidelines (WCAG), maintained by the group that sets web standards. WCAG is built on four principles — content should be perceivable, operable, understandable, and robust — and it defines three conformance levels: A (the minimum), AA (the common target), and AAA (the strictest, rarely met in full). For almost every business site, Level AA is the goal, because it's both achievable and the level most laws and policies point to.

You don't need to memorize WCAG. You need to get right the handful of things that account for most real-world barriers — which is what the checklist below does. Accessibility overlaps heavily with plain good design, so many of these choices improve the site for everyone; our web design guide covers the broader design decisions they sit inside.

Why accessibility is worth your time

Four reasons, each concrete:

• Reach. The World Health Organization estimates that about one in six people worldwide lives with a significant disability. An inaccessible site turns away a real, sizable share of visitors — and their spending.
• SEO. The things screen readers rely on — descriptive alt text, a logical heading structure, meaningful link text, captions — are the same signals search engines use to understand a page. Accessible sites tend to be more findable.
• Usability for all. Strong contrast helps anyone reading on a phone outdoors. Captions help people watching video with the sound off. Clear labels help everyone.
• Legal risk. Rules vary by country, but the direction is one way. In the US, the Americans with Disabilities Act has been applied to websites in a rising number of lawsuits, and courts and regulators generally treat WCAG 2.1 AA as the yardstick. In the EU, the European Accessibility Act now requires many private-sector digital services to be accessible. This isn't legal advice — check your own obligations — but "we didn't know" is a weak position to argue from.

The core accessibility checklist

Work through these. Most are quick to check and quick to fix.

Color and contrast

• Text has enough contrast against its background. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (about 24px, or 19px if bold). Light-gray text on white is the single most common failure.
• Don't rely on color alone to carry meaning. If a required field is only marked in red, or a link is set apart only by color, colorblind users miss it. Add an icon, an underline, or a text label.
• Buttons, input borders, and meaningful icons meet a 3:1 contrast ratio too, so people can see where to click.

Images and non-text content

• Every meaningful image has descriptive alt text — a short phrase describing what it shows or does, so a screen reader can convey it. "Staff photographed outside our Cairo office," not "IMG_2043."
• Decorative images have empty alt text (alt="") so screen readers skip them instead of reading out filenames.

Keyboard and focus

• Everything works with a keyboard alone. Put your mouse aside and press Tab: can you reach and operate every link, button, menu, and form field? Many people cannot use a mouse at all.
• The focus indicator is visible. As you tab, a clear outline should show where you are on the page. Don't let a theme strip it out for looks.

Structure and navigation

• Headings are used in logical order — one H1, then H2s and H3s that nest properly. Screen reader users jump between headings, so structure isn't only visual.
• Link text describes where it leads. "Read our pricing," not "click here." A screen reader can list every link out of context, and vague ones become useless.
• The page declares its language (the lang attribute), so screen readers pronounce words correctly.

Forms

• Every field has a visible, associated label — not just placeholder text that disappears the moment someone types.
• Errors are explained in words, positioned near the field they refer to — "Enter a valid email address," not a lone red border.

Media and motion

• Videos have captions, and ideally a transcript; audio needs a transcript.
• Anything that moves, blinks, or auto-plays can be paused or stopped, and nothing flashes rapidly, which can trigger seizures.

How to test your site without special software

You can catch most issues yourself in under an hour:

1. The keyboard test. Put the mouse away and Tab through a key page — your homepage, a product page, your contact form. If you can't reach something, or you lose track of where you are, that's a barrier a real visitor hits too.
2. A contrast checker. Free browser tools and online checkers let you paste in two colors and read the ratio. Test your body text, your buttons, and any pale gray captions.
3. An automated scanner. Free tools like WAVE, the axe browser extension, or the Lighthouse accessibility audit built into Chrome scan a page and list issues in priority order. Treat the result as a starting point, not a final grade.
4. A screen reader pass. Every major operating system ships one for free. Close your eyes and try to complete a single task — find your phone number, submit the form. It's the fastest way to feel what's broken.

Automated tools catch perhaps a third to a half of issues; the keyboard and screen reader tests catch the human ones machines miss. Use both.

Fix in order of impact, not ease

Don't try to reach perfect conformance in one sprint. Start with the barriers that block people outright: keyboard access and a visible focus outline, form labels, and alt text on meaningful images — these decide whether someone can use the site at all. Then tidy contrast and heading structure, which affect a wide swath of visitors. Media captions and the finer points come next. Re-test after each batch. Accessibility is a standard you maintain, not a certificate you earn once: every new page, image, and PDF is a fresh chance to add a barrier back in, so fold these checks into how you publish.

FAQ

What is the difference between WCAG A, AA, and AAA?

They are conformance levels. A is the minimum and clears only the most basic barriers; AA adds the criteria most people actually rely on — contrast, resizable text, consistent navigation — and is the practical target for a business site; AAA is the strictest and often impossible to meet across a whole site. Aim for AA.

Is web accessibility legally required?

It depends on where you operate and what kind of organization you are. Many countries have laws that extend accessibility expectations to websites, and WCAG 2.1 AA is the standard most of them reference. Rather than gamble on whether you're exempt, treat AA as the baseline — it's good for business either way. This isn't legal advice; check your jurisdiction.

How do I make my small business website accessible?

Start with the checklist above: fix color contrast, add alt text to meaningful images, make sure everything works by keyboard with a visible focus outline, label your form fields, and add captions to video. Then test with a keyboard, a contrast checker, and a free scanner. Most fixes are edits, not a rebuild.

Does accessibility help SEO?

Yes — indirectly but meaningfully. Descriptive alt text, a logical heading structure, meaningful link text, and captions help search engines understand your content the same way they help assistive technology. Accessible pages are usually easier to find.

Can I just install an accessibility overlay widget?

Be skeptical. Overlay widgets that promise instant compliance from a single line of code are widely criticized by accessibility experts and disabled users, and they don't reliably fix the underlying problems — some make matters worse. There's no shortcut around the checklist; the real fixes live in your actual pages.

Next step

Accessibility isn't a mysterious technical hurdle. It's a short list of concrete checks — contrast, alt text, keyboard access, headings, forms, captions — that widen your audience, help your search visibility, and lower your risk, mostly with edits you make once. Run the keyboard test and a free scanner on your most important page this week, fix the barriers that block people outright, and build the checks into how you publish from then on.

If you'd like a partner to audit your site and build accessibility in properly rather than bolt it on later, see how TheAppCode can help.