Think about the last time you gave up on a website. Maybe the text was too faint to read. Maybe a button was too small to tap. Now imagine that happening to every visit.
That is daily life for many people with a disability, and for older users too. Making your site easier to use for them is good manners. It also tends to make the site better for everyone.
What web accessibility means
Web accessibility means building a site that people can use whatever their abilities. That covers vision, hearing, movement and thinking differences. It also covers someone using a keyboard instead of a mouse, or a screen reader instead of looking at the page.
The common reference point is the Web Content Accessibility Guidelines, known as WCAG. They are published by the W3C, the international body that sets web standards. WCAG 2.2 became a W3C Recommendation on 5 October 2023. You can read the full text on the W3C WCAG 2.2 page.
The three conformance levels
WCAG sorts its requirements into levels A, AA and AAA. A is the lowest and AAA is the highest. Meeting a level means meeting everything in the levels below it too.
The NSW Government’s digital team describes AA as the middle level, widely considered legally acceptable. It treats AAA as best practice. For most small business sites, aiming for AA is a sensible target. The NSW article on what WCAG 2.2 means explains the new criteria in plain terms.
WCAG 2.2 builds on version 2.1. It does not replace it. Content that meets 2.2 also meets the 2.1 requirements.
Four principles behind the guidelines
The guidelines rest on four ideas. Content must be perceivable, operable and understandable. The fourth principle is that it must keep working across different browsers and assistive tools.
In everyday terms, people need to be able to see or hear your content. They need to be able to use it with the tools they have. They need to understand it. And it should not break when the technology changes.
Practical fixes that matter most
You do not need to rebuild your site to make a start. A few changes cover a lot of ground. The fixes below are a good place to begin.
Add text alternatives to images
WCAG requires non text content to have a text alternative that serves the equivalent purpose. In practice, that means writing short, accurate alt text for images that carry meaning. A screen reader reads that text aloud.
Describe what the image shows and why it is there. Purely decorative images can use empty alt text so screen readers skip them. If you sell goods online, this goes hand in hand with your product images and descriptions.
Check your text contrast
At level AA, text needs a contrast ratio of at least 4.5 to 1 against its background. Large text needs at least 3 to 1. Pale grey on white fails this test very easily.
Free contrast checkers will test your colours in seconds. Your font pairings matter here too. A pretty typeface that is hard to read defeats its own purpose.
Make everything work with a keyboard
WCAG says all functionality should be operable through a keyboard interface. Try it yourself. Put the mouse aside and move through your site with the Tab key. Can you reach every menu, link and form field? Can you see where you are?
Make buttons and links easy to hit
Version 2.2 added a rule on target size. At level AA, tap targets should be at least 24 by 24 pixels, with some exceptions. It also asks that drag actions have a simple alternative, and that a focused item is not hidden behind other content.
WCAG 2.2 also covers logins. Sign in steps should not depend on a memory or puzzle test without an alternative. That is worth knowing if your site has customer accounts.
Writing clear content helps too
Accessibility goes beyond code and colour. The words on the page count as well. Short sentences and plain language help people with reading difficulties, and they help busy readers too.
Use headings in a logical order so the page has a clear outline. Write link text that says where the link goes. A link that reads “here” tells a screen reader user nothing when links are read out in a list.
Label every form field. A visitor should know what to type before they start typing. Explain any error message in plain words and say how to fix it.
Why this helps the business
An accessible site is easier to read and easier to use. Those habits tend to keep visitors on the page for longer. If people leave quickly, check your bounce rate and look at whether basic usability is part of the problem.
Clear structure also helps software that reads your pages. Our piece on building websites that machines can read covers how well organised content serves software as well as people. Many of the same habits apply.
Testing your own pages
You can learn a lot without special software. Zoom your browser to 200 per cent and see whether the page still reads properly. Turn off images and check that the page still makes sense.
Ask a few people outside your business to try the main task on your site. That might be booking a service or buying a product. Watch where they hesitate. Those spots are usually where a barrier sits.
Automated checkers are a useful first pass, but they catch only some problems. A human check on key pages still matters. Repeat the test whenever you add a new feature or redesign a page.
Where to start
Pick your five most visited pages. Test them for contrast, keyboard use and image descriptions. Fix what you find, then move on to the next group.
Small, steady improvements add up. Write them down so each new page you publish starts from a better base. Keep the list handy for anyone who edits the site.
Frequently asked questions
What is WCAG?
WCAG stands for Web Content Accessibility Guidelines. The W3C publishes them as the main international standard for accessible web content. The current version is WCAG 2.2.
Which level should a small business aim for?
Level AA is the usual target. The NSW Government describes it as widely considered legally acceptable, while AAA is treated as best practice. You can still adopt individual AAA items where they suit your site.
Do I need to follow WCAG 2.1 or 2.2?
WCAG 2.2 builds on 2.1, so meeting 2.2 also meets 2.1. The NSW Government suggests organisations already meeting 2.1 add the new 2.2 elements where possible. Starting with 2.2 on any new site is the simpler path.
Is this legal advice about my obligations?
No. Your obligations depend on your business and your circumstances. Speak with a qualified lawyer if you need advice on disability discrimination law.
This article is general information only and is not legal advice. Laws and processes change and can differ between states and territories. Speak with a qualified lawyer about your own situation.
