A website accessibility checklist for an existing site starts with a baseline: run an automated scanner, tab through every key page with the keyboard, and try one real task with a screen reader. Then fix the high-impact basics first, namely text alternatives, form labels, colour contrast, focus visibility and clear error messages, and retest after each round.
A website accessibility checklist: run a baseline check
You cannot prioritise fixes without knowing where you stand. Spend an hour on a baseline before touching any code.
- Pick the pages that matter. The home page, a typical content page, your contact or booking form, and any checkout or sign-up flow. Fixing these helps more people than polishing rarely visited pages.
- Run an automated scanner such as a browser extension or the accessibility panel in your browser's developer tools. Treat it as a starting list. Automated tools catch only a portion of problems, such as missing labels and low contrast, and cannot judge whether alt text is meaningful or whether a flow makes sense.
- Do a keyboard pass (described below) and a short screen reader pass.
- Record findings in a simple sheet: page, problem, who it affects, how hard to fix, and status. This becomes your fix list and your evidence of progress.
The reference for what good looks like is the Web Content Accessibility Guidelines (WCAG), published by the W3C. They are organised around content being perceivable, operable, understandable and robust. Use them as the yardstick, and consult the W3C's own materials for the exact wording of each success criterion. If you are planning a new build rather than fixing an old one, our article on building accessible websites with WCAG basics covers the design side.
Quick wins: alt text, labels and contrast
These fixes are usually cheap and affect many visitors.
- Alt text. Every informative image needs a short description of what it conveys, not what it is. A product photo might read as the product name and key visual detail. Purely decorative images should have empty alt text so screen readers skip them. Do not put text inside images without repeating it in real text.
- Headings. Use headings in a logical order that reflects the page structure, one main heading per page. Do not choose a heading level just for its size.
- Link text. Links should make sense out of context. Replace repeated phrases such as read more with descriptive text.
- Colour contrast. Check text against its background using a contrast checker, and compare the result with the ratios in WCAG. Light grey text and text over photographs are the usual culprits. Also do not rely on colour alone to convey meaning, such as red for errors with no text or icon.
- Text resizing. Zoom the page and enlarge the browser text size. Content should still be readable without things overlapping or disappearing.
- Page language and title. Set the page language and give each page a unique, descriptive title.
Keyboard walk-through
Put the mouse aside and use only the Tab, Shift+Tab, Enter, Space, Escape and arrow keys. Walk each key page and ask:
- Can you reach every link, button, menu and form control?
- Is the focus indicator always visible? If a stylesheet removes the outline, replace it with a clear alternative.
- Does the tab order follow the visual reading order?
- Can you open and close menus, dialogs and carousels, and does focus move into a dialog and return afterwards?
- Is there a way to skip repeated navigation and jump to the main content?
- Can you get out of every widget, or does it trap focus?
Anything that works only with a mouse hover or a drag gesture needs a keyboard equivalent. This single test often reveals the most serious blockers on a business site.
Forms and error messages
Forms are where inaccessible sites cost the most, because that is where people book, buy and ask for help. Check that:
- Every field has a visible label connected to it in the code, not just placeholder text that vanishes while typing.
- Required fields are stated in text, not by an asterisk alone.
- Instructions, such as password rules or date formats, appear before the field.
- Error messages say what went wrong and how to fix it, appear next to the field, and are announced to assistive technology. Moving focus to the first error or an error summary helps.
- Autocomplete attributes are set for common fields like name, email and address, which helps many users and reduces typing.
- Timeouts, if any, can be extended, and the form does not lose data on error.
Third-party widgets
Chat bubbles, cookie banners, booking embeds, maps, review carousels and video players are often the worst offenders, and you did not write them. Test them like everything else. If a widget traps focus, lacks labels or cannot be operated by keyboard, report it to the supplier and ask for a fix timeline. Check whether a newer version or an alternative provider handles accessibility better. As a fallback, provide an accessible alternative, such as a plain contact form or a phone number next to a booking widget. Include widget behaviour in your supplier checklist whenever you renew or choose a tool.
Accessibility statement
An accessibility statement tells visitors what you have done, what is known not to work yet, and how to ask for help. Whether you need one, and what it must contain, depends on your situation and jurisdiction, and requirements change, so confirm with qualified legal counsel rather than copying wording from another site. Whatever the legal position, a truthful statement with a working contact route is good practice. Keep it honest: do not claim full conformance unless you have properly tested for it, and update it when things change. The W3C publishes guidance on conformance and reporting that you can follow.
Screen reader testing, simply
You do not need to be an expert to learn a great deal. Use the screen reader already built into your computer or phone, turn the screen off or look away, and attempt one real task, such as finding opening hours or submitting an enquiry. Listen for missing labels, unclear link text, silent errors and confusing reading order. Note that different screen readers and browsers behave differently, and experienced users navigate in ways beginners do not. For anything high-stakes, involve disabled users or a specialist reviewer.
Keeping it accessible
Accessibility decays when nobody owns it. Add a few checks to your routine: an accessibility line in your launch checklist, alt text and heading checks in your editing guide, an automated scan when releasing changes, and a keyboard pass on new templates. Re-run your baseline after major redesigns, and track open issues. If the underlying templates are the problem, our guide to deciding between a redesign and a rebuild can help you judge whether patching is still the right call. If you want help turning findings into fixes, our page on software development for New York businesses explains how we work, and you can reach out through the contact page. Remember that this article is general guidance, not legal advice.
Frequently asked questions
Where should I start with an inaccessible site?
Start with a baseline: scan your most important pages with an automated tool, tab through them with the keyboard, and try one task with a screen reader. Then fix the basics that affect many visitors, such as alt text, form labels, contrast, focus visibility and error messages, retesting after each round.
Do I need an accessibility statement?
That depends on your situation and jurisdiction, and requirements change, so ask qualified legal counsel and check official sources. Regardless of the legal position, a truthful statement that lists known issues and offers a contact route helps visitors. Avoid claiming full conformance unless you have properly tested for it.
How do I test with a screen reader?
Use the screen reader built into your computer or phone and try a real task, such as finding opening hours or submitting a form. Listen for missing labels, vague link text, silent errors and odd reading order. Behaviour varies between tools, so involve disabled users or a specialist for important flows.