Accessibility
Web accessibility services: WCAG audits and fixes
An accessible site can be used by someone who cannot see the screen, cannot use a mouse or cannot tell red from green. In a growing number of countries, it is now a legal duty for many businesses as well.
Who needs an accessible website
Any business that wants every customer it can get. People with low vision, people who navigate by keyboard or voice, people with a tremor, older patients who zoom to 200% and anyone reading a phone in bright sun all use the same site. Accessible pages tend to be clearer for all of them, which is why accessibility is part of our UX design.
Some businesses also have a legal duty. The European Accessibility Act has applied since 28 June 2025 to many products and services sold to consumers, online shops and banking services among them. Your local law may also name a reference framework for checking a site, such as the RGAA, and require public bodies and some large companies to publish an accessibility statement based on it.
We are not lawyers. We tell you which standard fits your kind of site and test against it. Whether a law covers your business is a question for your legal adviser.
WCAG, RGAA and the European Accessibility Act
| What it is | Who it concerns | |
|---|---|---|
| WCAG | The W3C’s international guidelines, with levels A, AA and AAA; 2.2 is the current version | The technical base for most accessibility rules, including the two below |
| RGAA | A reference framework based on WCAG, with its own test method | Public bodies and some large companies where the law makes it the reference; they must publish an accessibility statement |
| European Accessibility Act | A directive applied through national laws since June 2025 | Many products and services sold to consumers, online shops included; microenterprises providing services are exempt |
How an accessibility audit works
Choose the sample
Home page, each main template, forms, the booking flow and, for stores, the checkout. Templates repeat, so their fixes do too.
Automated scan
Tools quickly catch missing labels, contrast failures and broken markup. They miss a large share of real problems, so this is only the start.
Manual tests
Keyboard only, screen readers such as NVDA and VoiceOver, zoom to 200% and 400%, and every form filled in and sent with deliberate errors.
Report
Each issue with its WCAG criterion (and RGAA criterion where that framework applies), where it occurs, how to fix it and how urgent it is.
Fix
Our developers fix it, or yours do from the report. We work alongside them on the hard parts.
Re-test and statement
We re-test the fixes and, where needed, help you write the accessibility statement.
Problems we find most often
Low contrast
Grey text on white and text over photos. Level AA asks for a contrast ratio of at least 4.5:1 for normal text.
Images without useful text
Missing alt text, or alt text that says “image” or repeats the file name.
Forms built for the eyes
Fields without labels, placeholders used as labels, errors shown only in red.
Keyboard traps
Menus, pop-ups and cookie banners that a keyboard user cannot reach or cannot leave, and focus outlines removed for style.
Booking calendars
Date pickers that need a mouse. A booking flow that blocks keyboard users blocks appointments.
Arabic pages
Missing lang and dir attributes, so screen readers read Arabic with the wrong voice and in the wrong order.
What you receive
- An audit report with the WCAG criterion, and the RGAA criterion where relevant, for each issue
- A fix list ranked by impact on real users and by effort
- Fixed templates and components, if we do the work
- Re-test results after the fixes
- A draft accessibility statement where you need one
- A short guide for content editors: headings, link text, alt text, documents
Frequently asked questions
Does the European Accessibility Act apply to my business?
It applies to many products and services sold to consumers, ecommerce among them, and exempts microenterprises that provide services. The details depend on what you sell, where you sell it, and your size. We tell you which standard to test against; a lawyer confirms whether the law covers you.
Is an automated scan enough?
No. Automated tools catch part of the problems, mostly the easy ones. Keyboard traps, a confusing reading order and unclear forms need a person to test them.
Which level should we aim for?
WCAG level AA. It is the level laws and contracts usually refer to, and the RGAA covers it. Level AAA is rarely required for a whole site.
Do you audit Arabic and right-to-left pages?
Yes. We check language and direction attributes, reading order, mirrored layouts and how screen readers handle mixed Arabic and Latin text.
How often should we re-test?
After any redesign or new template, with spot checks as content is added. An editor can break accessibility with one unlabelled image or a heading out of order, so we include checks in website maintenance.
Last updated · By the Napexy team
Keep reading
Tell us where you want to grow.
A 30-minute call with a strategist. You get a plan in plain words and a fixed quote, whether or not you work with us.