The accessibility fixes that matter most
The seven changes that remove the most real barriers on a small business website, ranked by who they unblock rather than by how easy they are.
Accessibility guidance tends to arrive as a list of eighty items with no indication of which ones matter. That is how it ends up ignored.
These seven are the ones that, in practice, unblock the most people on a typical small business website. They are ordered by who they stop, not by how quick they are to do.
1. Everything must work with a keyboard
If it can be clicked, it must be reachable and operable with Tab and Enter. This is the highest-impact item on the list because it affects people using screen readers, switch devices, voice control, and anyone whose hands do not work well with a mouse.
The common failures: custom dropdowns built from divs, modal dialogs that let focus escape behind them, carousels that only respond to swipe, and menus that only open on hover.
Test it yourself in two minutes. Put your mouse away and Tab through your own site. If you cannot reach the menu, open the form, or close the popup, that is your first job.
2. Do not remove the focus outline
Somewhere in almost every stylesheet is a rule that removes the focus ring because a designer thought it looked untidy.
That outline is how a keyboard user knows where they are. Removing it makes the entire site unusable for them while looking perfectly fine to everyone else, which is why it survives so long.
Style it if the default is ugly. Never delete it.
3. Real labels on form fields
A placeholder is not a label. It disappears when someone starts typing, is often too low-contrast, and is not reliably announced by screen readers.
Every input needs a visible, associated label. Error messages need to say what is wrong in words, be associated with the field, and not rely on colour alone to indicate which field failed.
Forms are where accessibility failures cost you money directly, because a form nobody can complete is a customer who went elsewhere.
4. Headings that describe structure, not size
Screen reader users navigate by heading, the way a sighted reader skims. That
only works if the headings are real headings in the right order: one h1, then
h2 for sections, h3 beneath those.
Text made large and bold to look like a heading is invisible to that navigation.
Choosing h3 because h2 was too big is the same mistake in reverse; set the
level by structure and control the size with styling.
5. Enough colour contrast
Text needs to stand out from its background: 4.5:1 for normal text, 3:1 for large text and meaningful interface elements. Light grey on white fails, and it is everywhere, usually because it looked elegant on a designer’s calibrated monitor.
This one is genuinely easy to check with a tool and genuinely affects a lot of people, including anyone reading outdoors on a phone.
6. Alt text that carries the meaning
Not a description of the picture. The information the picture conveys.
A photo of your team needs “The team outside the Athabasca shop.” A decorative swirl needs empty alt text so it is skipped entirely. An image of a chart needs the finding in words, or a table nearby.
The common failure is a filename, or the word “image”, both of which are worse than nothing.
7. Video captions, when you have video
If you publish video with speech, caption it. Auto-generated captions are a starting point and need correcting, particularly for names and technical terms.
This benefits more people than expected: most social video is watched with the sound off.
What to do with this list
Work down it in order on the pages that matter most, which for almost every business is the home page, the contact page and whatever the main conversion path is. Fixing three pages properly beats a shallow pass over forty.
None of these require a redesign. All of them are the kind of thing that costs nothing when built in from the start, which is the argument for caring about it during a build rather than after one.
What this list does not replace
Getting these right removes most of the common barriers, and it is not the same as conformance. If you have a legal obligation or a contract requiring WCAG 2.1 AA, you need testing with real assistive technology and a written report, which is what an audit involves. Whether that applies to you is covered in the rules Canadian businesses should know.
If you want these seven done on your site without becoming an expert in them, send us the address.
Related: accessibility rules in Canada, how to choose a web developer, and our accessibility work.
Further reading
Topics in this article
Get new articles by email
One email when something new goes up, roughly twice a month. Plain writing on what software costs and what is worth building. No sequences, no sales calls, and one click to leave.
Keep reading on the same subject
-
What an accessibility audit involves
What gets tested in a WCAG audit, why automated scans miss most of it, what the report should contain, and what the whole thing costs.
See what is tested -
The accessibility rules Canadian businesses should know
Who is legally required to meet WCAG in Canada, what the deadlines are, and what applies to a small business with no legal obligation at all.
Check what applies -
How often does a website actually need updating?
Separating the updates that matter from the ones that do not: security patches, content, design refreshes, and how often each genuinely needs doing.
Get the real schedule