- Market
- Saudi Arabia
- Written for
- Head of Digital, COO
- Decision
- Build a site to the accessibility standard and test it against real assistive tools
- Languages
- EN · AR
The standard in practice
What each part of the WCAG standard asks, and what meeting it takes
The guidelines rest on four principles. None of them is met by a widget added at the end; each is a set of decisions taken in the markup and the design.
Perceivable — content the senses can take in
Text alternatives for images, captions for media, and colour contrast high enough to read; the content does not depend on sight or colour alone.
Who it serves: Users with low vision or a screen reader.
Operable — usable without a mouse
Every action reachable by keyboard, a visible focus order that follows the page, and no trap a keyboard user cannot leave.
Who it serves: Keyboard-only and motor-impaired users.
Understandable — predictable and clear
Form fields with real labels, errors explained in words, the page language declared, and behaviour that does not surprise the user.
Who it serves: Users with cognitive load or a screen reader announcing state.
Compatible — works with assistive technology
Valid, well-structured markup with roles used correctly, so the fourth principle holds and screen readers keep interpreting the page as they and browsers update.
Who it serves: Every assistive tool that reads the page.
The false fix
The accessibility overlay that passed the scan and failed the user
The tempting shortcut is an overlay — a script dropped onto a finished site that claims to make it accessible in a line of code. It often lifts an automated score, which is why it sells. But an automated scan checks only the fraction of accessibility a machine can measure; it cannot tell whether a screen reader can actually complete a form, whether the focus order makes sense, or whether a keyboard user can escape a menu. An overlay that raises the score while a real user still cannot use the site has fixed the number, not the site.
Real accessibility is structural. It lives in the markup that gives a screen reader the shape of the page, the labels that make a form usable, the focus order that follows the layout, and the contrast chosen at design time. Those cannot be sprayed on afterwards, which is exactly why building them in from the start is cheaper than the retrofit — and why we test with the tools a disabled visitor actually uses rather than trusting a scan that measures the surface. The standard exists to describe a usable experience; passing it should mean the experience is usable, not that a widget said so.
Where it is usually lost
The parts of a site where accessibility is most often lost
The static text of a page is rarely the problem. Accessibility breaks in the interactive and the complex — and these are the parts a scan is least able to judge.
Forms and their errors
A form is where accessibility most often fails: fields without real labels, errors shown only by colour, and validation a screen reader never announces. If a user cannot tell which field is wrong and why, they cannot complete it.
Custom components
Menus, tabs, sliders and modals built from scratch usually lose the keyboard and screen-reader behaviour that native elements give for free. They need the roles and keyboard handling added deliberately, or they become traps.
Media and moving content
Video without captions, audio without a transcript, and animation a user cannot pause each shut someone out. Accessible media is planned, because captions and transcripts are content that has to be produced, not a setting to toggle.
Content that updates without a reload
When part of a page changes on its own — a filtered list, a live total, a notification — a screen reader may never announce it. Dynamic updates have to be signalled so a user who cannot see the change still learns of it.
Our role
What we build and test, and where a formal conformance claim sits
We build to the standard and test against it. We are clear about the difference between that and a formal certification, which is a separate exercise.
- 01
Built to the standard from the start
We build the markup, the components and the design to the WCAG guidelines from the first line, so accessibility is a property of the site rather than a layer added over a finished one.
- 02
Tested with real assistive tools
We test with screen readers and keyboard-only navigation alongside automated scans, because the scan measures the surface and the manual test measures whether a person can actually use the page.
- 03
The formal claim stays separate
A formal conformance statement or an independent audit is a distinct step, and we do not issue one on your behalf; we build and test to the standard so an independent assessment starts from a site that is genuinely close to it.
Whether you pursue a formal conformance claim, and who audits it, are your decisions; we build and test the site to the standard so that when an independent assessment is done, it is measuring a site that was made accessible rather than one dressed to pass.
Common questions
What buyers ask
Is our website legally required to be accessible in Saudi Arabia?+
Public-sector and public-facing digital services are held to the Kingdom’s digital-government accessibility expectations, which draw on the WCAG guidelines. Whether a specific private site carries a legal obligation depends on your sector and how the service is classified, and that is a question for your own legal advisers rather than one we would answer for you. What we can say plainly is that the practical case for accessibility does not wait on the legal one: an inaccessible site turns away customers, staff and partners who use assistive technology, and building to the standard is far cheaper than retrofitting under pressure later. We build to the guidelines regardless of where the legal line falls for you.
Can you just add an accessibility widget to make our existing site compliant?+
We do not, because it does not work in the way it promises. An accessibility widget or overlay is a script laid over a finished site; it can raise an automated score, which is why it is sold, but it cannot supply the structure real accessibility needs — the markup a screen reader relies on, the labels a form needs, the keyboard behaviour of a custom component. Users of assistive technology frequently find overlays make sites harder to use, not easier. The honest route for an existing site is an audit that names the specific failures and their structural causes, then fixing those in the site itself. It is more work than a widget and it produces a site that a disabled visitor can actually use, which the widget does not.
How do you test that a site is actually accessible, not just passing an automated scan?+
By using the site the way a disabled visitor would. An automated scan is a useful first pass — it catches missing alt text, low contrast and some markup faults quickly — but it can only measure the portion of accessibility a machine can check, which is a minority of it. So alongside the scan we test manually: navigating the whole site with only a keyboard to confirm every action is reachable and no focus is trapped, and going through the key journeys with a screen reader to confirm a form can be completed, an error understood and a dynamic update announced. The difference between the two is the difference between a site that scores well and a site a person can use, and only the manual test tells you which one you have.
In this cluster
Audit your accessibility
An accessibility audit of your current site that names the specific failures, the structural cause of each, and what it takes to build the fix in rather than paint it over.
Start the conversation
