Accessibility checks a small business can do without special tools
Use everyday browser and phone checks to find barriers before commissioning a specialist audit.
Test real tasks first
Accessibility is easier to understand when you test what people actually need to do. Choose three or four important journeys: find a service, read opening hours, request a quote, book an appointment, buy something or contact support. Test those journeys on the homepage, a service page, a form and a confirmation step.
Do not assume that a page is accessible because it looks tidy. A visitor may be unable to reach a menu with a keyboard, understand a form error or zoom text without losing the button. Write down where you get stuck, what you expected and what happened. This turns a general concern into a fixable issue.
Include different devices and browsers when possible. A quick check on a laptop and phone can reveal problems that are invisible in a design review. Ask someone unfamiliar with the website to complete a task without coaching; their hesitation often shows where instructions are unclear.
Check keyboard and focus
Unplug the mouse or simply leave it untouched. Use Tab to move through links, buttons, fields and menus. Shift and Tab should move backwards. Enter or Space should activate controls where expected. Can you open the main navigation, reach every form field and submit the task without a pointer?
Watch the focus indicator. A visible outline or other clear change should show where you are. If focus disappears against the background, a keyboard user can lose their place. Check that focus does not jump unexpectedly or become trapped inside a menu, dialog or cookie panel.
Look for a sensible order. The sequence should follow the visual and informational order of the page. A keyboard user should not reach a hidden footer link before understanding the main offer. If a component behaves strangely, record its name and location for the developer rather than trying to redesign it yourself.
Review zoom, contrast and text
Use browser zoom to enlarge the page to 200 percent. Text should remain readable, controls should remain usable and important content should not disappear behind horizontal scrolling. Test a service page, contact form and navigation because responsive failures can appear in only one template.
Look at text against backgrounds in normal light and on a phone outdoors. Pale grey text, text over images and low-contrast buttons are common problems. Do not rely on colour alone to show errors, status or required information. Add words, icons with labels or another visible distinction.
Check font size, line length, spacing and paragraph density. Accessibility is not only a colour calculation; people need to locate and understand information. Plain language, descriptive headings and short paragraphs help visitors with different reading and cognitive needs.
Inspect headings, links and images
Read the headings without reading the paragraphs. They should describe the page structure and allow someone to find the relevant section. There should normally be one clear page title, followed by logically nested sections. Do not choose a heading only because its visual style looks attractive.
Read links out of context. “Read more” repeated several times does not tell a screen reader user where each link goes. Use descriptive phrases such as “See bathroom renovation examples” or make the surrounding sentence provide the missing context. Check that links distinguish destinations and actions.
Ask whether each image has a purpose. Important information in an image needs an equivalent text explanation. Decorative images should not create noisy or repetitive descriptions. A quick content review can identify missing, generic or keyword-stuffed alternative text even before a technical tool is used.
Test forms, media and mobile use
Submit a form with fields empty, with an invalid email and with deliberately long text. Can you tell which field needs attention? Is the error connected to the field and written in understandable language? Labels should remain visible or clearly associated when a field receives focus.
Check audio and video. Important spoken information needs captions or a transcript, and autoplay can disorient or inconvenience visitors. Make sure play, pause and volume controls are reachable with keyboard and touch. If a video is decorative, do not let it hide the essential written explanation.
On a phone, test portrait and landscape, larger text settings, touch target spacing and sticky elements. Make sure chat buttons, banners and cookie controls do not cover the page or trap the user. Ask whether someone can complete the main task with one hand and a slow connection.
Record, prioritise and escalate
Create a short issue list with page, task, barrier, evidence, severity and suggested owner. Prioritise barriers that block a core task, affect many pages or prevent contact and payment. Fix wording, labels, focus and contrast issues early; they are often smaller than a redesign and improve the experience quickly.
Do not claim that a checklist proves full compliance. Standards, assistive technologies and real users reveal issues a simple review misses. Arrange specialist testing when the website is central to the business, when complaints repeat, after a major redesign or when legal risk is material.
Repeat the checks after fixes and keep a record of decisions. ChatBuild can help a small business build accessibility into content, page structure, forms and mobile journeys so an audit starts from a stronger, more usable website.
Sources
- Introduction to Web Accessibility · W3C
- Easy Checks · W3C
- Google Lighthouse · Google Lighthouse
Frequently asked
- Can a small business test accessibility without software?
- Yes. Keyboard navigation, browser zoom, phone testing, heading review, form checks, captions and plain-language review reveal many common barriers. They do not replace specialist testing.
- What should be tested first?
- Test core tasks such as finding a service, contacting the business, booking or buying. Include the pages and forms used to complete those tasks.
- How do I test keyboard accessibility?
- Use Tab, Shift-Tab, Enter and Space without a mouse. Check that focus is visible, ordered and never trapped or lost.
- Is good colour contrast enough?
- No. Contrast matters, but accessibility also includes structure, language, forms, focus, alternatives, media, zoom and mobile interaction.
Sjors Hooijen Builds ChatBuild and writes about getting a business online without turning it into a project. Questions about this article? Email hi@chatbuild.com.