How to audit a small business website for accessibility
A practical accessibility audit for Australian small businesses: test the customer journey, prioritise barriers and improve the site without rushing into a rebuild.
A customer finds your business, opens the contact form and tries to ask for a quote. The page looks fine, but they cannot see where keyboard focus has moved. The form rejects an answer without explaining why. They leave.
That is a website problem, not just a compliance checkbox. An accessibility review should establish whether people can complete important tasks using different devices and ways of interacting. For most small businesses, the best place to begin is the enquiry, booking or purchase journey—not an expensive redesign.
This guide explains a focused first audit, what to test manually, where automated checks help and how to decide which fixes matter most. It is practical technical guidance, not a certification or legal opinion.
Start with the customer task, not an accessibility score
Pick one high-value journey: find a service, understand the offer and submit an enquiry. For an online shop, use product selection through checkout. For a service business, use the service page through confirmation of a submitted form.
Record each step, including the error path. A form that works with perfect inputs but gives no useful feedback when a required field is missed has not been properly tested.
Before testing, write down what success looks like:
- A visitor can understand the page's purpose and find the next action.
- They can operate controls without a mouse.
- Labels, instructions and errors are understandable.
- The page remains usable when text is enlarged or the screen is narrow.
- The visitor receives a clear confirmation when the task succeeds.
Do not assume a green automated audit means these tasks work.
Five manual checks worth doing first
1. Navigate with the keyboard
Put the mouse aside. Use Tab and Shift+Tab to move through links, menus and form controls, and Enter or Space to activate them as appropriate.
Can you tell which control has focus? Does focus move in a sensible order? Can you open and close the menu without getting trapped? Does an overlay or fixed banner completely hide the focused control?
The WCAG 2.2 guidance on focus visibility includes a Level AA criterion requiring a focused component not to be entirely obscured by author-created content. This is different from merely seeing article text pass underneath a sticky header while scrolling.
2. Complete the form with mistakes
Submit the form empty, enter an invalid email and correct the fields. Check whether each error identifies the problem in words and is associated with the relevant input. Make sure success is announced clearly rather than relying on a colour change or a disappearing button.
A real form can fail even when every field technically has a label: the labels may be unclear, required fields may not be explained, or an error may appear far from the field that needs attention.
If enquiry emails are critical, test the delivery and recovery path too. The guide to automating website enquiries without rebuilding covers what happens after a form is submitted; accessibility determines whether the customer can submit it in the first place.
3. Check mobile controls and zoom
Try the journey on a phone, then at enlarged text settings or browser zoom. Look for clipped content, overlapping buttons, horizontal page scrolling and controls that are difficult to tap.
WCAG 2.2 Level AA's Target Size (Minimum) criterion generally requires pointer targets of at least 24 by 24 CSS pixels, subject to exceptions such as sufficient spacing and inline text links. It does not mean every link in a paragraph must be turned into a 24-pixel square. For important actions, larger comfortable targets are often a better design choice.
4. Inspect headings, links and images
A heading should explain the section that follows, not simply look large. Links such as “Read more” become confusing when their destination is unclear outside the surrounding visual card. Images that convey meaning need useful text alternatives; decorative images should not create noise for screen-reader users.
Try reading the page's heading structure and link names without looking at the visual layout. If the content becomes difficult to navigate, the markup may need attention.
5. Test with assistive technology
Use a screen reader such as VoiceOver or NVDA for the core journey. Listen for the page title, headings, link names, form labels, error feedback and confirmation.
A screen-reader pass is not proof of full accessibility, and one device cannot represent every user's experience. It is a valuable check alongside keyboard, zoom and mobile testing. For a consequential service or a complex interface, involve people with disabilities in usability testing where possible.
Where automated tools help—and where they stop
An automated checker can flag missing labels, some contrast problems, invalid semantics and other detectable issues. It can speed up triage across a larger site.
It cannot reliably decide whether a service explanation makes sense, whether a multi-step form is understandable, or whether the right error message appears after a failed submission. Automated tools also cannot establish that every user can complete a task.
Use automation to find candidates for investigation, then reproduce important problems manually. Record the page, steps, expected behaviour, observed behaviour and impact. A screenshot without reproduction steps is much harder for a developer to fix.
Prioritise fixes by blocked tasks and business impact
Not every finding deserves the same urgency. A practical order is:
- Blocked journey: a customer cannot submit a form, complete checkout or access essential information.
- Major friction: keyboard focus is unclear, errors are difficult to resolve, or important controls are hard to use.
- Repeated pattern: the same issue appears in a shared navigation, form component or template across many pages.
- Local improvement: isolated wording, spacing or decorative issues that do not prevent the task.
Consider reach and effort alongside severity. Fixing one shared form component may remove the same barrier from several pages. Changing an isolated marketing animation may be less urgent.
Avoid using a single numerical score as the prioritisation rule. A page can score well while the one action that earns the business enquiries remains unusable.
Does an Australian small business need WCAG 2.2?
The Australian Human Rights Commission's April 2025 guidelines explain accessibility in the context of obligations under the Disability Discrimination Act and recommend recognised digital accessibility standards. WCAG 2.2 Level AA is a sensible technical benchmark for a modern website, but it is not accurate to describe every individual WCAG success criterion as a separately legislated rule for every private business.
The W3C's WCAG 2.2 guidance provides the actual criteria and explanations. If your business has contractual, government procurement or sector-specific requirements, check those separately with an appropriate adviser.
The practical point is simpler: customers should not be excluded from essential tasks because the website assumes everyone sees, taps or navigates in the same way.
Fix the existing website before commissioning a rebuild
An accessibility problem does not automatically justify replacing WordPress, Shopify or a custom website. First identify whether the barrier comes from content, a shared component, a plugin, a theme or the underlying platform.
For example, an enquiry form with unclear errors may need better labels, validation messaging and focus management—not a new CMS. A site-wide navigation problem may justify replacing one component. A heavily customised legacy checkout with inaccessible dependencies may need a larger intervention.
That is why a focused Website Audit should produce a prioritised remediation plan, not just a long defect list. If the existing platform is sound, Website Growth & Care can provide a way to implement and retest improvements over time.
When replacement is genuinely being considered, use the rebuild-versus-modernise decision guide to separate structural limitations from issues that can be repaired in place.
A manageable two-week starting plan
In the first few days, select the main customer journey, run keyboard and mobile checks, test form errors and use an automated checker to identify candidates. Capture reproducible findings and identify which components are shared.
Next, fix the issues that block the journey. Retest with the same steps and, where possible, a second input method or assistive technology. Record what was corrected, what remains and who owns follow-up checks when content or plugins change.
The outcome should be a website that more people can actually use, with a clear next round of work—not a certificate based on one automated scan.
If your website is losing enquiries or a redesign is being proposed, start with a practical website audit or get in touch. The first decision is what needs fixing, what can stay and how to verify that the important journey works.