Most small business owners think about accessibility only when someone tells them a page is hard to read or a form will not submit. By then, a customer has already given up. An accessible website is simply one more people can use: someone on a phone in bright sunlight, someone zoomed in to 200 percent, someone who navigates with a keyboard, or someone using a screen reader.
The good news is that you do not need a dedicated web team to make real progress. Below is the checklist we work through when we build and review custom websites for Australian businesses. It is written so you can run most of it yourself.
Why accessibility matters for a small business
There are three plain reasons.
First, it is about customers. If a person cannot read your prices, find your phone number or complete your booking form, you lose that enquiry, whatever the reason.
Second, it overlaps heavily with good usability. Clear headings, readable text, sensible contrast and forms that explain their errors help everyone, not only people with a disability.
Third, there is a legal angle. In Australia, the Disability Discrimination Act applies to services delivered online, and the Australian Human Rights Commission points businesses to the Web Content Accessibility Guidelines (WCAG) as the benchmark. We are not lawyers and this is not legal advice, but WCAG 2.2 at Level AA is the widely accepted target and a sensible goal for most sites.
Start with the pages that earn you money
Do not try to audit every page at once. Pick the pages where people make a decision:
- Your home page
- Your main service or product pages
- Your contact, quote or booking form
- Your checkout, if you sell online
Most sites are built from a handful of templates, so fixing one service page template often fixes every service page at the same time.
Run the free automated checks
Automated tools will not catch everything, but they find the obvious problems in minutes.
- Open your page in Chrome, right-click, choose Inspect, then run a Lighthouse report with only Accessibility ticked.
- Try a second tool, such as the WAVE or axe browser extensions, to compare results.
- Save each report with the date so you have a record of what you checked and what you fixed.
Look for the usual suspects: low-contrast text, images with no alt text, form fields with no label, links and buttons with no readable name, and a page that does not declare its language.
Test it like a real visitor
This is the part tools miss, and it takes about fifteen minutes per page.
- Keyboard only. Put the mouse aside and press Tab through the page. Can you reach every link, menu item and form field? Can you always see where you are? Can you open and close the menu and any pop-ups?
- Zoom. Zoom the browser to 200 percent. Text should reflow and stay readable without sideways scrolling.
- Phone. Use the page on a real phone. Are buttons big enough to tap? Is the phone number a tap-to-call link?
- Forms. Submit a form with a field left blank. Does the error message say what went wrong, next to the field, in words rather than only a red outline?
- Media. Videos should have captions, and nothing important should autoplay with sound.
If you can, ask someone who uses a screen reader every day to try your booking or contact form. One short session usually teaches more than any report.
Fix problems where they live
When you find an issue, fix it at the source so it stays fixed.
- Fix colours and font sizes in the theme or design system, not page by page.
- Make alt text part of your upload routine. Describe what the image shows and why it is there. Decorative images can have empty alt text.
- Write link text that says where the link goes. “View our services” beats “Click here”.
- Use real headings in order (H1, then H2, then H3) rather than bold text that only looks like a heading.
- Be careful with accessibility overlay widgets. They can change how a page looks, but they do not fix the underlying code, so treat them as an extra, not a fix.
Keep it accessible after launch
Accessibility is not a one-off project. Every new page, image, PDF and plugin can bring problems back. A light routine works for most small businesses:
- Re-run your automated checks after any design change or new template.
- Spot-check one key page with the keyboard each month.
- Add accessibility to your brief whenever you hire a designer or developer, and ask which WCAG version and level they build to.
- Publish a short accessibility statement that tells people how to contact you if something does not work.
When we design and code a site, we build it mobile-first and accessible from the start, because retrofitting is always harder than getting the structure right on day one. Options like high-contrast modes and text resizing can also be built in where your audience needs them.
FAQ
Do small businesses in Australia need an accessible website?
The Disability Discrimination Act applies to online services, and WCAG 2.2 Level AA is the widely used benchmark. Check your own obligations with a qualified adviser, but aiming for AA is a sensible default.
Can an accessibility plugin make my site compliant?
Not on its own. Overlays and plugins can help with some settings, but issues in your code, content and forms still need fixing directly.
How long does a basic accessibility check take?
For a small site, running automated tools and a keyboard test on your four or five key pages can usually be done in an afternoon. Fixing what you find depends on how the site was built.
Is accessibility only for people with a disability?
No. Clear contrast, readable text, labelled forms and keyboard support make a site easier for everyone, including people on phones, older visitors and anyone in a hurry.
Want a second pair of eyes?
If you would like us to look at how your site handles accessibility, or you are planning a new site and want it built right from the start, call us on 1300 360 148 or start a brief online. The discovery call is free.