Website Accessibility: What to Fix First on Your Site

Most owners I meet are not against website accessibility. They have simply never been told what it asks of them, so it sits in the too hard basket next to privacy policies and terms of service, and it stays there until something forces the issue.

That is a shame, because the first round of fixes is mostly an afternoon of unglamorous editing, and it makes the site work better for every visitor rather than only for the people it currently turns away. Thirteen years in, I have never met an owner who regretted doing this. I have met plenty who put it off for two years and then found out what that cost them.

What follows is the version I give in the first conversation: what website accessibility actually means, who is being shut out of a typical Australian small business site without anyone intending it, the four principles behind every fix, the five changes I would make first, and how far a free browser tool will get you before you need a person.

What Website Accessibility Actually Means

The definition, in one plain paragraph

The clearest definition is not mine, and it is worth reading once in full: "Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them." That is the W3C's own wording, from the group that writes the guidelines, and it settles most arguments. It is about use. A site that looks impressive but cannot be operated by someone using a keyboard is not accessible, and a plain site that everyone can use is. Nothing in that sentence mentions appearance, and nothing in it is a matter of taste.

Why the web was built to work for everyone

The other half of the W3C's introduction is the part owners find surprising, because it is a statement about design intent rather than about disability: "The Web is fundamentally designed to work for all people, whatever their hardware, software, language, location, or ability." The flexibility is original. Anyone can read a page on a phone, a television, a screen reader or a magnifier, at any size, because the underlying standards were built that way. Most of us then remove that flexibility one shortcut at a time. We fix the text at a size that suits our own monitor, pick two greys we can tell apart on a good screen, and label a form field with a hint instead of a name.

What it is not: a badge or a certificate

It is not a badge, and it is not a certificate you hang on the site afterwards. I do not offer certification and I am not going to pretend the topic has a finish line, because it does not. A site that is accessible this month can stop being accessible the moment somebody adds an image with no description or a booking form with no labels. What you are building is a habit, and a site that more people can use than last month.

Who Your Website Is Hard To Use For

Why this is not a narrow audience

Start with the official figures rather than with a guess. The Australian Bureau of Statistics reported that "5.5 million Australians (21.4%) had disability, up from 17.7% in 2018." That comes from the ABS release dated 4 July 2024 describing 2022, so read it as the position at that time rather than as this year's number. One in five adults is not a niche you serve as a favour. Add everyone whose eyesight, hearing or steadiness is changing with age, and the group a typical small business site has to work for is a large share of its customers.

The barriers people actually hit

The scale of the problem is not really in dispute. WebAIM's 2026 report on the accessibility of the top 1,000,000 home pages found that "95.9% of home pages had detected WCAG 2 failures." Two caveats belong with that figure, and I would rather state them than let you over-read it. The sample is the top million home pages in the world, not Australian small business sites, and only automatically detectable failures were counted, so a page that scores well is not automatically a page that works. Take it as evidence that this is normal and fixable, not as a verdict on your site. In practice the barriers are ordinary things: a light grey caption on a white background, an image that means something with nothing behind it for anyone who cannot see it, a form field identified only by its placeholder text, a menu that only opens on a mouse hover, and a link that says "click here" with no clue where it goes.

Why your oldest customers feel it first

Because small changes in vision and hearing arrive slowly, and the web got smaller and quieter in the meantime. Text that was comfortable a few years ago is now a caption. A supplier's phone number set in light grey on white is readable on a bright monitor and unreadable on a phone in a car park. The person who cannot read it rarely complains. They ring somebody else, or they give up on the page and ask a family member, and you never hear about it. The reason I put this section before the fixes is that owners tend to picture a stranger when they picture this customer. The more common case is somebody they already know.

The Four Principles Behind Every Fix

Every fix in the next section comes back to one of four questions. The W3C sets out four principles behind them, which sounds formal until you translate each one into plain English and use it as a test.

Perceivable: can they get the content at all

Can the information reach the person in some form they can take in? A photograph of a printed price list fails here, because the words in it are not available to a screen reader or to anyone who needs to enlarge text. An image with a description behind it passes, because the meaning survives even when the picture does not.

Operable: can they use it without a mouse

Can somebody move through the page, open what they need and submit the form without a mouse? Press the Tab key on your own home page and watch where the outline goes. If it disappears halfway through, or jumps past the enquiry form, or never appears at all, that is the whole answer. Plenty of people navigate by keyboard, by voice, or with a device that behaves like a keyboard.

Understandable: does it behave predictably

Does the site do what it looks like it will do? This is where the boring writing problems turn into access problems. A form that fails with the words "invalid input" has told the person nothing about which field is wrong. A button labelled "submit" next to another labelled "send" makes people guess. An error message that appears far from the field it refers to is worse than no message at all.

Built to last: does it work with their own tools

Does the page still make sense with a screen reader, a magnifier, a voice control program or an older browser somebody cannot upgrade? This is the principle that covers the invisible plumbing: labels attached to fields rather than sitting near them, headings used as headings rather than as big bold text, and buttons built as buttons. It is also the one you cannot test by looking at the page, which is why it gets skipped.

The Five Fixes I Would Make First

If you do only five things, do these. They are ordered by how much they help for the effort they cost, and none of them needs a developer to explain it to you first.

Alt text on the images that carry meaning

Behind every image there is a short description that a screen reader will read out instead of showing the picture. When that description is missing, the person hears nothing at all, or hears something that means nothing to them. Write what the image is doing for the page. A photo of the team gets a line about who is in it. A photo that only decorates a heading gets nothing, because adding words for decoration just adds noise to everything the person has to listen to. This is a words problem, not a technical one, and that is exactly why it is the single cheapest fix on the list.

Text contrast you can actually read

This is the most common failure on the web and the easiest to correct, because you are changing a colour rather than rebuilding a page. WebAIM's 2026 report found that "Low contrast text, below the WCAG 2 AA thresholds, was found on 83.9% of home pages, an increase from 79.1% in 2025", counting automatically detectable problems on the top one million home pages. The standard itself is unusually specific: WCAG 2.2 says "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1" for normal text, and it allows a lower bar for large text, because "Large-scale text and images of large-scale text have a contrast ratio of at least 3:1". Read that as a threshold to design against rather than as a claim about your own site. The practical version is blunter: a light grey paragraph on a white background is the most likely thing to fail on an Australian small business site, and a darker grey is usually all it takes.

Form labels, error messages and instructions

Your enquiry form is the one page where failure costs money immediately. Every field needs a label that is attached to it, not a hint that disappears as soon as somebody starts typing. Errors need to say which field is wrong and what would fix it. Instructions need to sit before the field rather than after it. And every field needs to be reachable by keyboard alone, in an order that matches the way the form reads. Test your own form with a screen reader on a phone if you can, or simply submit it with obvious mistakes in it and read what comes back.

Headings that run in the right order

People using a screen reader often move through a page by jumping between headings, the same way a sighted reader scans the bold lines. That only works if the headings are real headings in a sensible order: one main heading for the page, then level two for the sections, then level three inside them, with no level four used to make text bigger. When a heading is faked by making a paragraph bold and large, the jump list is empty and the page becomes a wall of undifferentiated text.

Page titles and link text that say where they go

Every page needs a title that makes sense on its own, because it is what gets read out first and what somebody sees when they have six tabs open. And every link needs words that describe its destination. "Click here" and "read more" tell a person nothing unless they can see the words around them, which is exactly what they cannot do. "See the delivery options" works everywhere, on screen and read out loud.

How To Check Your Own Site In An Afternoon

The free checks worth running first

The W3C publishes a review process for exactly this situation, and its own description of it is modest on purpose: "This page helps you start to assess the accessibility of a web page." Start there rather than with a paid tool or a quote. Alongside it, four things you can do yourself today. Zoom the page to 200 per cent and check that nothing overlaps or disappears. Tab through the page without touching the mouse and watch where the focus outline goes. Pick your two most important pages and read them out loud, slowly, imagining somebody cannot see the screen at all. And check the contrast on your grey text against its background, which any free contrast checker will do in seconds.

What a browser extension will and will not catch

An automated checker is a good first pass and a bad final answer. It will reliably find a missing description on an image, a low contrast pair of colours, a form field with no label, a heading level used out of order and a page with no title. Those are mechanical faults, and they are common on most sites. What it cannot tell you is whether the description you wrote is any use, whether the error message makes sense to a person who is worried about their booking, or whether the order of the page still makes sense when it is read aloud. The tool that produces the report is honest about its own limits, noting that automated checks cannot detect every failure and that a page with no detected errors is not automatically an accessible page.

Where automated checking stops and judgement starts

The judgement layer is where an owner's knowledge of the business is worth more than any tool. Is this the sentence a customer needs first? Does this label describe the field the way our customers describe it? If a person cannot see the picture, what do they need to know about the product it shows? That is why I do the first pass with a browser tool and the second pass by reading the page as a person, and why a report that nobody has read is worth very little.

What The Work Actually Costs A Small Business

What drives the effort on a typical site

Effort is driven by how many different page designs the site has, not by how many pages it holds. A site with eight pages built from one template often takes a day. A site with two hundred pages built from nine templates is a far bigger job, and most of that effort goes on finding every place the shared template is repeated, because some of those places hide inside a page builder. The other driver is who can make the change. If your site is edited through a tool you understand, you can fix the text-level items yourself. If every change has to be requested from somebody who bills by the hour, the arithmetic changes.

The template fix versus the content fix

This is the single most useful distinction for keeping the cost sane. A template fix happens once and applies to every page built from it: the body colour, the form labels, the heading levels, the link styling, the focus outline. A content fix happens on one page and only on that page: the description behind an image, an error message, a page title, the words on a link. Do the template work first, because it removes the same problem from every page at once, then work through content on the pages that matter commercially. The rest of the site can wait its turn.

When paying someone is the cheaper option

Put the question back on your own numbers rather than on mine. What is one enquiry worth to you, and how many of your pages actually produce one? If a relatively small number of enquiries would cover the work, the decision is easy, and for most businesses the deciding factor is time rather than money: the fixes are not difficult, but they are the kind of task that gets moved to next month indefinitely. That is the practical site work side of what I do, for owners who would rather it was simply done. If you want to understand the effort before you spend anything, tell me what your site is built on and I will tell you where the effort really sits, which is usually clear within a few minutes of looking at the templates.

Does Accessibility Help Your SEO As Well

Where the two genuinely overlap

In a few dull places, and they are worth naming honestly. Search systems and screen readers both work from the text rather than the picture, so a description behind an image helps both. Both rely on real headings, a title that says what the page is, and link text that describes a destination. When those things are done properly, accessibility and search visibility are the same work done once. That overlap is real, and it is much smaller than the way it usually gets sold.

Where they do not help each other

A search engine cannot tell whether your grey text is hard to read, and it will not reward you for darkening it. Keyboard navigation, focus outlines, error messages and form labels are largely invisible to the way a page gets ranked. You can hold the first position for your main search term and still have an enquiry form that a person using a screen reader cannot complete. The reverse is also true, so this is not a zero-sum trade: the two jobs touch each other in a handful of places and ignore each other in most of them.

Why I will not sell it as an SEO tactic

Because it would be a dishonest reason to do the work, and it tends to produce the wrong fixes. If the goal is rankings, an owner ends up writing descriptions stuffed with search phrases instead of describing the image, which makes the page worse for the person listening to it. I would rather you did these things for the customer who cannot read the caption, and take the search benefit where it genuinely exists. If the technical side of your site is the real question, the technical checks that decide whether anything on the page can be read by anything at all is the right place to start, and it is a different job from this one.

The Mistakes I See Small Businesses Make

Looking for a plugin that fixes everything

There is no plugin that makes a site accessible, and the ones that claim it are the most expensive mistake on this list. An overlay toolbar sitting on top of the page does not add a description to an image, does not label a form field, and does not fix the reading order, because those things live in the page itself. It can also get in the way of the tools people already use. Spend the same effort on the five fixes instead.

Fixing the home page and stopping there

I see this constantly, and it is understandable, because the home page is the page everybody looks at. But the home page is rarely where the money is. The pages that matter are the enquiry page and the two or three service pages that bring the enquiries in, which are exactly the pages owners look at least. Do those first and the home page later.

Putting it off until the next redesign

This is the one that costs the most, because a redesign is the worst possible time to fix accessibility. You will be making decisions about colour, type and forms while trying to get a site live, and the accessibility work will lose every argument to the launch date. Every fix described here can be made on the site you have now, in a month of small sessions, without touching the structure or changing a single address.

Your First 30 Days On This

Week one: list and measure

Pick two pages that matter commercially, your enquiry page and your highest value service page. Run them through an automated checker and keep the list of failures, then do the four manual checks from earlier. Do not try to fix anything in week one. You are producing the list that makes the next three weeks cheap, and it is the step most people skip, which is why their fixes end up scattered and unverifiable.

Weeks two to four: fix the five basics

Work through the five fixes in order, on those two pages first. Contrast, then the descriptions behind the images that carry meaning, then the form, then the heading order, then the titles and the link text. If the same problem appears on every page, fix it in the template rather than page by page. When the two pages are clean, a proper look at the whole site, once the basic fixes are in place, is a sensible next step, because it will show you how much of the rest is template work and how much is one-off editing.

What to add to your monthly routine

Once a month, submit your own enquiry form and read what comes back, check any image added in the past month has a description behind it, and read your newest page out loud. That is about ten minutes. It is also the difference between a site that gets more usable over time and a site that quietly slides back to where it started, one skipped description at a time.

Frequently asked questions

What does website accessibility actually mean?

It means the site is built so that people with disabilities can use it, not just look at it. W3C's own words are the clearest ones available: "Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them." The reason it keeps coming up is in the sentence next to it, because "currently many sites and tools are developed with accessibility barriers that make them difficult or impossible for some people to use." Read those two together and the topic stops being abstract: most sites are not hostile, they are just built without asking who might be using them.

Is this a legal requirement for my business?

I am not the right person to answer that, and nothing here is legal or disability compliance advice. Even so, the question is usually asked the wrong way round. The owners who get value from this work do it because a fifth of the adults in this country live with a disability, not because somebody might one day ask them about it. Compliance and legal obligations sit with someone qualified to advise on them, and I would rather point you there than guess.

Where do I start if I have no budget for it?

Start with the two pages that matter commercially and run the free checks yourself. W3C publishes a starting point for exactly this situation, and its own description of it is modest on purpose: "This page helps you start to assess the accessibility of a web page." Contrast and image descriptions alone are worth the effort, and the numbers say why: WebAIM's most recent report found "95.9% of home pages had detected WCAG 2 failures", and the most common problem was that "Low contrast text, below the WCAG 2 AA thresholds, was found on 83.9% of home pages, an increase from 79.1% in 2025." Those are home pages of the top one million sites, not Australian small businesses, and only automatically detectable problems were counted, so read them as a sign that this is normal and fixable rather than as a score for your site.

What is a realistic first fix if I can only do one thing?

Contrast, because it is the most common problem and the standard is unusually clear. WCAG 2.2 states that "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1" for normal text, with a lower bar for large text. In practice that means a light grey paragraph on a white background is the single most likely thing to fail on an Australian small business site, and it is also the easiest to fix because you are changing a colour, not rebuilding a page. If you fix nothing else this month, fix that.

Will it cost me traffic or rankings?

Losses come from redesigns and from technical changes, and neither is required here. Almost everything described here is editing: the words behind an image, a colour value, a label, a heading level, a line of link text. None of that changes your addresses, your structure or your content, and your rankings are not resting on a light grey caption. Where accessibility and search do genuinely overlap it is in the dull places, meaning a text alternative that describes an image and a link that says where it goes, and I would rather you did those for the person using a screen reader than for a search engine, because that is the honest reason.

How long does this take?

The first pass is an afternoon and the rest is a habit. Two pages, a list of ten problems and the five fixes above is genuinely a half day of work if someone sits down and does it. What takes longer is the second half, which is the templates behind every page, and that is where a site with two hundred product pages behaves very differently from a site with eight pages. I am not going to put a number of weeks on it, because it depends entirely on how the site was built, and anyone quoting you a timeline before looking at your templates is guessing.