Website strategy
Website Accessibility Checklist for a Small Business
Improve website accessibility with practical checks for keyboard use, headings, contrast, forms, images, video, motion, and mobile layouts.
- Direct answer
- Full process
- Real example
- Clear checks
The short answer
The aim is a site where more people can perceive the content, understand it, navigate it, and complete important actions. Start by documenting the present situation, then make one decision at a time. A tool should support the workflow; it should not be used to avoid deciding how the workflow works.
Accessibility is often presented as a technical extra. In practice, it is part of making a website understandable and usable. Clear labels help a person using assistive technology, but they also help someone completing a form quickly on a phone in bright sunlight.
You do not need to pretend one checklist proves perfect compliance. Start with the highest-impact barriers, test with real interactions, and keep accessibility inside the normal design and content process.
The aim is a site where more people can perceive the content, understand it, navigate it, and complete important actions. If a step does not change what somebody knows, decides, or does, it probably does not belong in the process.
The complete process
Work through these stages in order. It is tempting to jump to the visible part, but most expensive revisions begin in an earlier decision that nobody finished.
Use a logical page structure
Give every page one descriptive main heading, organise sections in order, and use real heading elements rather than styling ordinary text to look large. Add landmarks for header, navigation, main content, and footer.
Ready to move on when: A screen reader outline and a visual scan tell the same story.Make keyboard use complete
Navigate with Tab, Shift+Tab, Enter, Space, and Escape. Focus must be visible, order must be logical, menus and dialogs must work, and no control should trap the user.
Ready to move on when: Every action can be reached and completed without a mouse.Check text and colour
Use readable type, sufficient contrast, clear link styling, and more than colour alone to show status or errors. Let users zoom without text overlapping or disappearing.
Ready to move on when: Content remains readable at 200% zoom and states are understandable without colour.Label forms properly
Connect visible labels to fields, explain required formats, identify errors near the relevant field, preserve entered data, and make success confirmation clear. Placeholder text should not do the job of a label.
Ready to move on when: A user knows what went wrong and how to fix it.Write useful image and media alternatives
Give informative images concise alternative text, leave decorative images empty for assistive technology, caption meaningful video, and provide transcripts where audio carries information.
Ready to move on when: Important meaning is available without seeing or hearing the media.Respect motion and mobile use
Support reduced-motion preferences, avoid flashing content, keep touch targets large enough, and test orientation and responsive reflow. Sticky tools must not cover forms or navigation.
Ready to move on when: The site remains calm and usable on a small screen and with motion reduced.A realistic example
Consider a contact form with grey placeholder labels, red-only errors, and a submit button that cannot receive keyboard focus. It may look clean in a mockup, yet it blocks several users. Visible labels, descriptive errors, strong focus styles, and a real success message improve accessibility and reduce ordinary form abandonment at the same time.
Where people usually make the wrong turn
Adding an accessibility overlay and assuming the underlying site no longer needs work
Adding an accessibility overlay and assuming the underlying site no longer needs work. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
Writing alt text that repeats file names or says “image of” without conveying purpose
Writing alt text that repeats file names or says “image of” without conveying purpose. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
Testing only automated scores and never completing the site with a keyboard or screen reader
Testing only automated scores and never completing the site with a keyboard or screen reader. Stop, identify the decision that is missing, and correct the source of the problem before adding more tools or content.
How to know the work is improving
Do not collect numbers simply because a dashboard can show them. Pick a small set that reflects the outcome and review it on a schedule long enough to make a sensible decision.
- Completion of keyboard and zoom test scripts
- Form error and abandonment rate
- Number of accessibility issues found before release versus after launch
We can review the current setup, clarify the workflow, design the customer-facing experience, build the required system, and support the work after launch.
Before you call it finished
- The main decision and responsible owner are written down.
- The mobile journey has been completed from beginning to end.
- Claims, prices, dates, links, and permissions have been checked by the right person.
- Tracking measures the intended outcome rather than activity alone.
- Someone owns maintenance, review, and follow-up after launch.
Questions people ask before starting
Does an automated accessibility score prove the site is accessible?
No. Automated tools catch some issues; manual keyboard, screen-reader, zoom, content, and user testing are still necessary.
Is accessibility only for large companies?
No. The usability principles apply to every site, while legal duties vary by location and organisation. Obtain legal advice for your specific obligations.
Should every image have alt text?
Every image needs an appropriate text alternative decision. Decorative images usually use empty alt text; informative images need useful descriptions.
References and further reading
Policies and platform features change. Use these sources to verify requirements that affect your implementation, then apply them to the real business context.