Updated 9 September 2026 · 3 min read
Quick answer: A practical website accessibility checklist should cover readable contrast, meaningful headings, keyboard access, visible focus, image alternatives and understandable forms. Review complete tasks, not just isolated pages. Automated checks can identify some issues, but manual testing is also needed to understand how the website works for people.
Where should a small business begin?
Choose the journeys that matter most: finding a service, reading its details and making contact. Review the homepage, a typical service page, a blog article and the contact form. Reusable components such as navigation and buttons deserve attention because one issue can affect many pages.
Record each problem with a location, a reproduction step and the task it interrupts. This turns an abstract accessibility goal into a manageable improvement list. Fix barriers that stop people completing essential tasks before minor visual inconsistencies.
Is the text readable against its background?
WCAG 2.2 Level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, subject to defined exceptions. These are measurable ratios, not a judgement that a colour “looks dark enough.” Check text over images, gradients and hover states as well as plain backgrounds. See W3C’s explanation of minimum text contrast.
For a dark website, pay particular attention to muted descriptions and fine borders around controls. A brand can keep its visual character while choosing text colours that remain easy to read.
Can people understand the page structure?
Use headings to describe the organisation of the content. A main heading introduces the page; section headings and subheadings explain what follows. Avoid choosing a heading level only because of its default font size. W3C recommends nesting headings by rank and avoiding confusing jumps; see the headings tutorial.
Can the main journey be completed with a keyboard?
- Use Tab and Shift+Tab to move through links and controls.
- Check that the current focus is visible and follows an understandable order.
- Open and close menus and other interactive elements.
- Complete the contact form and recover from an error.
- Confirm that no component traps the visitor or hides the focused control.
This is a practical review sequence, not a complete conformance audit. Include people who use assistive technology in testing when possible, especially for complex interactions.
What should images and forms communicate?
Write image alternatives around the image’s purpose in context. Avoid repeating nearby text unnecessarily or describing a decorative background as if it were essential content. A chart carrying important information also needs a readable explanation of its message.
Make form labels and instructions understandable before someone starts typing. An error should explain what needs to change, rather than only changing the field’s colour. W3C’s form-label guidance explains how labels should identify and be associated with their controls.
Frequently asked questions
Does passing an automated test mean the site is fully accessible?
No. A passing result only covers the checks the tool performed. Review reading order, interaction and complete tasks manually too.
Is this checklist a legal compliance assessment?
No. It is a practical design review. Formal conformance evaluation and any legal obligations require assessment of the actual site and its context.
Pair this with the mobile design checklist, or discuss an accessible webdesign project with Stefano Marketing Agency.
