Website Accessibility Standards in South Africa

South Africa has no dedicated website accessibility law. There is no statute saying your website must meet WCAG, no regulator issuing accessibility fines, and no compliance deadline in the diary. Any supplier telling you otherwise is either mistaken or selling something.

What South Africa does have is a constitutional equality clause, an Equality Act that lists disability as a prohibited ground, and public sector guidelines that are recommendations rather than requirements. That is the honest legal position, and it is the weakest possible reason to think about accessibility at all.

The argument for building an accessible website in this market is a commercial one, and it survives the absence of a law entirely.

The law being quoted at you does not exist

Search for website accessibility in South Africa and within a few results you will find agencies and overlay vendors citing the Rights of Persons with Disabilities Act as the legislation governing digital accessibility in this country.

There is no such Act.

South Africa ratified the United Nations Convention on the Rights of Persons with Disabilities in 2007. Turning that into a dedicated domestic statute has taken rather longer. In October 2024, seventeen years after ratification, the South African Law Reform Commission called for input on a discussion paper towards disability-specific legislation, the proposed Promotion and Protection of Persons with Disabilities Bill. A discussion paper is not a bill before Parliament, and a bill before Parliament is not an Act. The disability-specific law that South African businesses are repeatedly told already governs them is still in the law reform pipeline.

This matters for a practical reason rather than a pedantic one. When a supplier gets the legal basis of their own pitch wrong, that tells you what kind of supplier they are. It also produces two bad outcomes for the buyer: either you purchase something out of manufactured fear, or you check, find nothing, and write off the entire subject as marketing noise. The second outcome is the more common one, and it is the more expensive.

What South African law actually says

Section 9 of the Constitution makes disability an enumerated ground in the equality clause. The Promotion of Equality and Prevention of Unfair Discrimination Act 4 of 2000, usually called PEPUDA or the Equality Act, operationalises that right and establishes the Equality Courts as the forum. PEPUDA prohibits any act or omission that withholds benefits, opportunities or advantages from a person on a prohibited ground, and disability is one of those grounds.

That is a general anti-discrimination framework. It was not drafted with focus indicators and checkout flows in mind, and it does not name WCAG anywhere. Whether a specific inaccessible commercial website amounts to unfair discrimination under PEPUDA is not a settled question in South African law, and we are not aware of a reported South African judgment that has decided it.

On the public sector side, the position is clearer and considerably more modest than most people assume. The Government Communication and Information System publishes website guidelines for national departments, and the accessibility guideline recommends that departments conform to at least Level A of WCAG 2.2. Two words there carry all the weight: recommends, and Level A. Level A is the lowest conformance level. It is the set of criteria that stops a website being unusable, not the set that makes it usable.

The GCIS page is worth reading for a second reason. It lists 1.4.3 Contrast (Minimum) among its Level A criteria, when the W3C classifies that success criterion at Level AA. If the official national guidance is imprecise about which criteria sit at which level, expecting a small business to navigate this as a compliance exercise is optimistic.

The statistic in every accessibility pitch is fifteen years old

Almost every South African accessibility article quotes a single figure for disability prevalence, usually around 7.5 percent. The trouble is not that the number is wrong. It is that no single number means much here, because Statistics South Africa reports prevalence on three different measures and they differ by a factor of nearly five.

Statistics South Africa published the Census 2022 comparison on 12/07/2024, in the report Profiling Socio-economic Status and Living Arrangements of Persons with Disabilities in South Africa, 2011 to 2022. It measures prevalence three ways, and the results are more useful than the number being circulated.

Under the United Nations measure, which counts people aged five and older reporting a lot of difficulty or an inability to function in one of six domains, prevalence is 6.0 percent. Under the severe measure it is 3.4 percent. Under the broad measure, which counts anyone reporting some difficulty, a lot of difficulty or an inability across seeing, hearing, communicating, walking or climbing stairs, remembering or concentrating, and self-care, prevalence is 15.7 percent. Prevalence declined on all three measures between the two censuses.

For a web build, the broad measure is the one that matters, and it is the one nobody quotes.

A person reporting some difficulty seeing is not registered as disabled anywhere and has never opened a screen reader. They are the 58 year old commercial property broker who can no longer read 13 pixel grey body copy on a phone in a car park. A person reporting some difficulty remembering or concentrating will not persevere through a four step checkout that clears their inputs on a validation error. Neither of those people is a legal exposure. Both of them are lost revenue, and both of them are in your target market right now.

Accessibility is a build quality problem wearing a compliance costume

Here is what the compliance framing obscures. The overwhelming majority of accessibility defects we find on South African business websites are not exotic. They are the same defects that damage conversion, mobile usability and search performance for every visitor, disabled or not.

• Body text below a 4.5:1 contrast ratio, usually because a designer chose light grey for a heading colour and the developer applied it to paragraphs. Typography and legibility decide more conversions than most briefs allow for.
• Form fields with a placeholder and no label, so the purpose of the field disappears the moment the user starts typing into it.
• Images carrying real information with empty alt attributes, which is an accessibility failure and a wasted semantic signal in the same stroke. The same structure that assistive technology reads is the structure that AI answer engines parse when deciding what to cite.
• Tap targets smaller than 24 by 24 CSS pixels, a criterion added in WCAG 2.2, which fails constantly on mobile navigation designed at desktop width.
• Heading levels chosen for how large the text renders rather than what the document structure actually is.
• Custom dropdowns, accordions and modals assembled in a page builder out of div elements and click handlers, fully operable with a mouse and completely inert with a keyboard.
• Carousels that advance automatically and cannot be paused.

Every item on that list is also a usability defect, a conversion defect, or both. That is not a coincidence. WCAG is in large part a formal description of interfaces that behave predictably, and interfaces that behave predictably convert better. The keyboard user and the impatient buyer on an LTE connection in Fourways are failed by the same code.

This is why the compliance frame is actively unhelpful in the South African market. It files accessibility as a legal cost with no deadline attached, which means it never gets budget. Framed as build quality, it is simply part of what a competent website design and build process already does, and almost all of it costs nothing extra at build time. It costs a great deal to retrofit, which is a separate argument and the reason this decision belongs at the start of a project rather than the end.

The overlay widget is not a fix, and a regulator has said so on the record

The most common response to accessibility in South Africa is to install an overlay: a script that adds a floating accessibility button offering high contrast, larger text and a screen reader mode.

On 03/01/2025 the United States Federal Trade Commission announced a proposed complaint and order requiring accessiBe to pay USD 1 million to settle allegations that it misrepresented what its accessWidget product could do. The complaint alleged that accessiBe claimed installing one line of code made a website compliant with 30 percent of WCAG requirements immediately, and started an AI process that made it fully compliant with the remaining 70 percent within 48 hours. According to the FTC, accessWidget in a number of instances failed to make basic components including menus, headings, tables, images and recordings compliant and accessible. The Commission issued its Decision and Order on 21/04/2025 and announced final approval on 22/04/2025. accessiBe agreed to the consent order without admitting liability, and the order runs for twenty years with annual compliance reporting.

South Africa has no equivalent regulator policing this, so nothing prevents the same products being sold here on the same claims. Treat the FTC record as free due diligence.

The structural problem is simple. An overlay runs on top of the markup. It cannot repair a heading hierarchy that was never built, it cannot label a form field the developer never labelled, and it cannot make a div behave like a button. What it reliably does is add a visible badge announcing that accessibility has been dealt with, which is worse than doing nothing, because it stops the real work ever being scoped.

Where this stops being optional

Three situations turn accessibility from good practice into a requirement with consequences attached, and all three are live for South African businesses right now.

• Selling into the European Union. The European Accessibility Act applied from 28/06/2025 and reaches businesses placing covered products and services on the EU market regardless of where the business is domiciled. Consumer ecommerce is squarely in scope. Conformance is assessed against the harmonised standard EN 301 549, which currently references WCAG 2.1 Level AA. Penalties are set by each member state rather than centrally, and the single EU wide fine figure that circulates in vendor marketing does not appear in the Directive itself. If you run a WooCommerce store shipping to consumers in the EU, this is not theoretical, and it is the one hard date that has already passed.

• Selling to government. The GCIS guidance is a recommendation for departments, but departments still have to answer for it, and accessibility questions increasingly turn up in supplier and bid documentation alongside the compliance material every South African supplier already assembles.

• Selling to large corporates. Vendor onboarding at the larger South African organisations, banks in particular, now routinely covers digital accessibility in the same questionnaire as POPIA and information security. Answering that question honestly is easier if the answer is not no.

If you want to know where your current website actually stands, the useful first step is not an automated scan. It is an hour with a keyboard, no mouse, trying to complete the one action the website exists to produce. Most South African business websites fail that test inside two minutes, and the failures are almost always cheap to fix and expensive to ignore.

Frequently Asked Questions

Is website accessibility a legal requirement in South Africa?

No. South Africa has no dedicated website accessibility statute and no regulator issuing accessibility penalties. Disability is a prohibited ground of discrimination under Section 9 of the Constitution and under PEPUDA, but neither instrument names WCAG or sets a technical standard for websites. Public sector guidance from GCIS recommends WCAG 2.2 Level A for government departments, and a recommendation is not a requirement.

Does South Africa have a Rights of Persons with Disabilities Act?

No, despite being widely cited by accessibility vendors. South Africa ratified the UN Convention on the Rights of Persons with Disabilities in 2007, but has not enacted disability-specific domestic legislation. The South African Law Reform Commission called for input on a discussion paper towards a proposed Promotion and Protection of Persons with Disabilities Bill in October 2024. That process is ongoing.

What WCAG level should a South African business website meet?

For most South African businesses, WCAG 2.2 Level AA is the sensible target for a new build because the work is cheap at build time. For an existing website, the practical answer is to fix the Level A failures that block users outright, then decide on Level AA on commercial merit. If you sell into the European Union, EN 301 549 currently references WCAG 2.1 Level AA and that is your floor, not your target.

Do accessibility overlay widgets make a website compliant?

No. An overlay runs on top of existing markup and cannot repair a missing heading structure, an unlabelled form field, or a control built without keyboard support. In January 2025 the United States Federal Trade Commission announced a USD 1 million settlement with overlay vendor accessiBe over allegations it misrepresented its product’s ability to deliver WCAG conformance. The Decision and Order was issued on 21/04/2025, runs for twenty years, and bars the company from claiming its automated products can make any website WCAG compliant without evidence to support it.

Does the European Accessibility Act apply to South African businesses?

It can. The European Accessibility Act applied from 28/06/2025 and covers businesses placing products and services on the EU market irrespective of where they are based. A South African online store selling to consumers in the EU is in scope. Conformance is assessed against EN 301 549, and penalties are set by individual member states rather than at EU level.

Does website accessibility affect SEO in South Africa?

Indirectly but meaningfully. Semantic heading structure, descriptive alt text, meaningful link text and predictable page structure are simultaneously accessibility requirements and the signals search engines and AI answer engines use to parse a page. Accessibility work is not an SEO tactic, but competent accessibility and competent technical SEO overlap substantially.

How many South Africans are affected by website accessibility barriers?

More than any single commonly quoted figure suggests, because Statistics South Africa reports prevalence on three different measures. In its profiling report covering Census 2011 to 2022, published on 12/07/2024, prevalence is 6.0 percent on the United Nations measure and 3.4 percent on the severe measure, but 15.7 percent on the broad measure, which includes people reporting some difficulty seeing, hearing, remembering or concentrating. For website design, the broad measure is the relevant one.