Website accessibility means building your site so people with visual, hearing, motor or cognitive disabilities can use it too — readable text, working keyboard navigation, alt text on images. South Africa has no law that names WCAG directly, but the Constitution and the Equality Act point the same way, and roughly 3.3 million South Africans live with a disability.
What Does “Website Accessibility” Actually Mean?
In practice, it comes down to a handful of things: text that’s readable against its background, images that have a written description for people using screen readers, forms with proper labels, and a site that works if someone’s navigating with a keyboard alone rather than a mouse — something people with motor disabilities, and plenty of power users, rely on.
The internationally recognised standard is the Web Content Accessibility Guidelines (WCAG), now at version 2.2. It’s organised around four principles — content should be Perceivable, Operable, Understandable and Robust — and has three conformance levels, A, AA and AAA. Level AA is the one nearly every law or policy that references WCAG actually requires, and it’s the realistic target for a small business site.
Is There a Law That Requires This in South Africa?
Not explicitly, and this isn’t legal advice — but there’s no law-free gap either. South Africa doesn’t have dedicated website accessibility legislation the way the EU does (its Accessibility Act) or the US does (the ADA). What it does have is the Constitution’s equality and dignity provisions, the Promotion of Equality and Prevention of Unfair Discrimination Act (PEPUDA), and the Rights of Persons with Disabilities Act — none of which mention websites by name, but all of which are built on the principle that excluding people with disabilities from an ordinary service is a form of discrimination. South Africa is also a signatory to the UN Convention on the Rights of Persons with Disabilities, which explicitly names equal access to information and communication technology.
No South African court case has yet tested a small business website under these laws specifically. But “nobody’s been sued over it yet” is a different thing from “there’s no risk” — and it ignores the much simpler, much more immediate cost: customers who can’t use your site at all.
How Many of Your Customers Could This Actually Affect?
According to Stats SA’s Census 2022, around 6% of South Africans — roughly 3.3 million people, using the internationally comparable measure — live with a disability, down from about 7% in the 2011 census. That’s before you count people with temporary impairments (a broken arm, eye surgery recovery) or the everyday situational versions of the same barriers — someone glancing at their phone in bright sunlight, or browsing one-handed with a baby on the other arm. Accessible design tends to help all of them.
How Common Are Accessibility Problems on Real Websites?
More common than you’d hope. The 2026 WebAIM Million report — an annual automated scan of the top one million home pages worldwide — found detectable WCAG failures on 95.9% of them, averaging 56.1 errors per page. The same handful of issues account for the vast majority of problems every year:
- Low colour contrast — found on nearly 84% of home pages scanned
- Missing alt text on images — affecting over half of pages
- Missing or unlabelled form fields — affecting around half of pages
- Empty links or buttons — present but with nothing for a screen reader to announce
- No declared page language — breaks pronunciation for screen-reader users
The point isn’t to feel bad about this — it’s to notice that you’re very likely not starting from zero, and that most of the fixes are genuinely small.
What Can You Fix This Week, Without a Developer?
| Quick fix | Why it matters | How to check it |
|---|---|---|
| Add alt text to every image | Screen readers read this aloud instead of the image | Open each image in your media library and check the “Alt Text” field isn’t blank |
| Check text contrast | Light grey text on white is unreadable for many low-vision users | Use a free contrast checker (e.g. WebAIM’s) on your main body text and buttons |
| Label every form field | Screen readers need to announce what a field is for | Click into each field on your contact form and confirm it has a visible label, not just placeholder text |
| Test your tab key | Confirms keyboard-only visitors can reach every link and button | Unplug your mouse and tab through your homepage and contact form |
| Use real headings | Screen readers jump between headings to navigate a page | Check that section titles are set as H2/H3 in your editor, not just bold text |
When Should You Bring In a Specialist?
The quick fixes above will catch the biggest, most common issues. But a full WCAG 2.2 AA review — checking colour contrast ratios precisely, testing with actual screen reader software, reviewing video captions — is a more specialised job, worth it once your site is handling real transaction volume, serious lead generation, or if you’re a public-facing service business where exclusion carries real reputational weight (healthcare, education, government-adjacent work). For most small sites, working steadily through the quick-fix list above gets you most of the way there.
The Bottom Line
Accessibility isn’t a legal tick-box in South Africa the way it is in some other markets — but it is a real slice of your potential audience, and most of the common failures cost nothing but attention to fix. It also sits alongside the other “boring but important” website basics worth getting right — see our guides to Core Web Vitals and POPIA cookie consent for the others.
Not sure where your site stands? Get in touch and we can talk through a practical starting point.
This article is for general information and isn’t legal advice — speak to a qualified professional for guidance specific to your business.