Skip to content
digitalaudits.com.au

WCAG basics for small business

By · 5 min read · Published · Updated

WCAG basics for small business

Try filling in your own contact form with your eyes shut while your phone reads the page aloud. On a lot of small business sites, the screen reader announces “edit text, edit text, edit text, button”, and you have no way of knowing which box wants your name and which wants your phone number.

That’s how your site works for thousands of Australians every day. Around one in five people in Australia has a disability, and many more have ageing eyes or are squinting at a phone in bright sunlight. When they can’t read your text or tell what a form field is for, they leave, and you never hear about it.

Accessibility decides whether a large share of your customers can use your site at all. Most small business sites fail on the same handful of problems, and nearly all of them can be fixed without a redesign.

What WCAG is and why it matters

WCAG stands for the Web Content Accessibility Guidelines, the international standard for making websites usable by everyone, including people who are blind, people with low vision, people who are deaf and people with limited movement or cognitive disabilities. Level AA of WCAG 2.2 is the target most organisations aim for, and it’s the benchmark used by Australian governments and in disability discrimination complaints.

The Disability Discrimination Act applies to websites, and complaints to the Australian Human Rights Commission do happen. The Act doesn’t name a technical standard for private businesses, but WCAG is what a complaint would be measured against.

The business case is simpler than the legal one. Someone who can’t use your booking form can’t become a customer. Many of the same fixes help Google too, because clear headings and image descriptions help search engines understand a page as well.

The four principles behind it

WCAG is built on four ideas, and every rule in it traces back to one of them. Content has to be perceivable, meaning people can see or hear it: images have text descriptions and text stands out from its background. It has to be operable, so everything works with a keyboard and buttons are big enough to tap.

It has to be understandable, with clear language and forms that explain what they need and what went wrong. And it has to be robust, which means it works with assistive technology like screen readers, the software that reads a page aloud for people who can’t see it.

You don’t need to memorise the principles. They’re useful as a way of asking, for any part of your site, who might be shut out of it.

The problems most small sites have

Low colour contrast is the most common. Light grey text on white, or white text on a bright colour, is hard for many people to read. WCAG level AA asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text, and a free online contrast checker will tell you whether your colours pass. The fix is usually slightly darker text or a stronger background.

Images without descriptions come next. Screen readers read out an image’s alt text, a short written description attached to it. Without one, a blind visitor hears nothing useful, or a file name like “IMG_2041.jpg”. Describe what the image shows in a short phrase, and leave the alt text empty for purely decorative images so screen readers skip them.

Form fields without labels do the most damage, because they can stop someone contacting you at all. Placeholder text inside a box, like “Your name”, disappears as soon as someone starts typing and often isn’t read aloud. Every field needs a visible label connected to it, and error messages should say in words what went wrong, not only turn the box red.

Links and buttons that don’t say where they go cause trouble too. Screen reader users often skim a list of every link on the page, so “Click here” and “Read more” tell them nothing. Icon-only buttons, like a magnifying glass or a menu icon, need a text label for screen readers. Link text should describe the destination, such as “Read our pricing guide”.

Some people can’t use a mouse at all. Try moving through your site with only the Tab key and pressing Enter to select. If you can’t reach every link and form field, or can’t see where you are because the focus outline has been removed, keyboard users are stuck.

The last two are quick. Your page should declare its language, so screen readers use the right pronunciation, which is a one-line fix. And headings should form a logical outline, with one main heading and smaller ones for each section, because screen reader users jump between headings to find what they need.

How to get started

Run a free accessibility audit first. It checks many of these problems automatically and lists them in order of impact, so you know where to start.

Fix the quick wins yourself: alt text, form labels, page language and link wording can all be changed in most website builders without touching code. Then test your contact or booking form with only a keyboard, and again with a screen reader. Windows includes Narrator, NVDA is a free alternative, Macs and iPhones have VoiceOver built in, and Android phones have TalkBack.

Bring in a web developer or accessibility specialist for the harder parts, such as colour changes across a whole theme or menus that only open on hover. Your report gives them a clear list to work from. For phone visitors, our guide to making your phone number easy to tap covers a related fix that helps everyone.

What automated checks can’t tell you

Automated tools, including ours, catch a lot but not everything. They can tell you an image has no alt text, but not whether the alt text you wrote makes sense. A full WCAG audit needs a person testing with a keyboard and a screen reader. A good automated score means you’ve got the basics right, which is where most sites fall down.

Be wary of accessibility overlay widgets that promise one-click compliance. They don’t fix the underlying problems, and many disabled users find them get in the way.

Every barrier you remove is a customer who can now reach you.

Start with your contact form.

Want the full picture? See what our free accessibility audit checks

Common questions

Is WCAG compliance required by law in Australia?

The Disability Discrimination Act 1992 makes it unlawful to discriminate against people with disability, and that applies to websites. The law doesn't name a technical standard for private businesses, but WCAG 2.2 level AA is the benchmark used in complaints and by government.

What's the difference between level A, AA and AAA?

They're levels of conformance. A covers the most basic barriers and AA is the accepted target for most websites. AAA is the strictest and isn't expected for whole sites.

Can an accessibility overlay or widget make my site compliant?

No. Overlay widgets that promise one-click compliance don't fix the underlying problems, and many disabled users find them get in the way. Fixing the site itself is the only reliable approach.

How do I test my site with a screen reader?

Windows includes Narrator, and NVDA is free. Macs and iPhones have VoiceOver built in, and Android has TalkBack. Try filling in your contact form using only the screen reader and keyboard.

Run an accessibility audit

See your real results and the fixes that matter most.