TabSphere journal / Website design
Website usability and accessibility: a practical design review for small businesses
A concise, practical checklist to review your website for usability and WCAG‑aligned accessibility, with steps you can try in a single week.

Why this review matters for small businesses
Fact: UK government guidance requires public services to meet WCAG 2.2 level AA as a minimum and recommends inclusive design from discovery through to live service. Source guidance is written for public services but its principles reduce legal and commercial risk for any organisation and improve customer reach. (Fact source)
Suggestion: Treat accessibility as part of usability, making content easy to read, forms easy to complete and navigation predictable helps all customers, not only people using assistive technology. 1 2
A focused review you can do in a day
Steps: 1) Pick three core user journeys (find product, contact you, buy/quote). 2) Run an automated scan (colour contrast, missing alt text, obvious semantic errors) and note top 10 issues. 3) Do 30 minutes of manual checks: keyboard-only navigation, resize text to 200%, and try a screen‑reader summary (or a guided demo video) to identify broken labels or unclear actions.
Concrete advice: Use the automated scan as a triage, it finds common code-level issues quickly. Then use manual, task-based tests to discover real usability barriers that tools miss (for example unclear form error messages or confusing link text).
Source note: GOV.UK guidance recommends combining automated checks with manual tests and user research including disabled users to find real problems. 2
Key technical and content checks (quick checklist)
Content: meaningful link text, clear headings, visible focus indicators, and descriptive alt text for images. Forms: label elements explicitly, show inline error messages and explain how to fix errors.
Technical: ensure semantic HTML (headings, lists, buttons), ARIA only when necessary, and that the site works at common breakpoints and older browsers. Test with assistive tech where possible (screen readers and magnifiers).
Distinction: The checklist above is practical guidance; the W3C WCAG 2.2 documentation defines the normative success criteria your site can be measured against. Use WCAG as the standards reference and this checklist to prioritise fixes. 1 2
Design fixes that give the biggest return
Prioritise: 1) Clear information architecture and labelled CTAs, users must know what to do next. 2) Accessible forms, these are where people drop out most often. 3) Colour and contrast, improves readability for everyone.
How to decide: If a fix blocks a core journey (for example an inaccessible checkout form), treat it as high priority. If it’s a cosmetic issue with small visual impact, schedule it later. These are practice-based suggestions informed by GOV.UK emphasis on discovering issues in Discovery and Alpha phases, and WCAG concepts on perceivable/operable content. 2 1
A small task to try this week
Task (realistic): Choose your most visited page. Spend 90 minutes: run an automated accessibility scan; complete the page’s main purchase/contact journey using only the keyboard; increase text size to 200% and note layout breakages; record three usability problems and estimate how many hours to fix each.
Expected outcome: You’ll get a short list of 3, 8 concrete fixes to discuss with your developer or designer. This task helps separate quick wins (missing labels, contrast) from larger work (restructuring checkout flows).
Practical tip: Document each issue with a one-line impact statement (what fails), where it is (URL and element), and a suggested fix or who should fix it (content, front-end dev, designer). 2 1
Sources
Checked 2026-10-21.
