Accessibility audit for websites, apps and software
An accessibility audit tests your website, mobile app or business software against WCAG 2.2 AA and the European Accessibility Act, with automated checks, keyboard and screen reader testing by people, and real tasks such as signing up, searching and paying. You get a ranked fix list that names each failing element, the criterion it breaks and how to fix it, and we can make the fixes in your code. It is a practical way to reach customers who are shut out today and to meet the law that has applied since 28 June 2025.
- Fixed price, agreed before work starts
- A one-off job with no follow-on contract
- Logins stay in your company's name
Why companies ask for an accessibility audit now
The European Accessibility Act, Directive (EU) 2019/882, applies to listed products placed on the market and services provided to consumers after 28 June 2025 (Articles 2 and 31). The services include e-commerce services, consumer banking services, e-books and dedicated software, electronic communications, access to audiovisual media services, and the websites, apps, e-tickets and information of passenger transport (Article 2(2)). In plain terms: if you sell to consumers online in the EU, your shop and app are very likely in scope. (Official text read on 12 November 2026.)
There are transitional rules. Service providers may keep using products they lawfully used before that date to provide similar services until 28 June 2030, and service contracts agreed before 28 June 2025 may continue unchanged until they expire, but no longer than five years from that date (Article 32(1)). Microenterprises that provide services are exempt from the service requirements (Article 4(5)). Public sector websites and apps have their own rules under the Web Accessibility Directive (EU) 2016/2102, which has applied to all public sector websites since 23 September 2020.
The business case is simpler than the law. People who use a screen reader, a keyboard instead of a mouse, magnification, captions or voice control are customers. When they cannot finish a checkout, they buy elsewhere. Accessibility fixes also tend to improve the experience for everyone: clearer forms, better contrast, larger touch targets and pages that work on slow phones.
What we audit against
The technical yardstick is the Web Content Accessibility Guidelines (WCAG) 2.2, a W3C Recommendation, in the version dated 12 December 2024 (read on 12 November 2026). Level AA is the level European law and most procurement refer to. WCAG 2.2 added criteria that older audits miss, among them:
- 2.4.11 Focus Not Obscured (Minimum): the keyboard focus is not hidden behind sticky headers, consent banners or chat buttons.
- 2.5.7 Dragging Movements: anything done by dragging can also be done with a single pointer, such as a tap.
- 2.5.8 Target Size (Minimum): targets for pointer input are at least 24 by 24 CSS pixels, or spaced so they are not hit by accident, with listed exceptions.
- 3.2.6 Consistent Help: help options appear in the same place across pages.
- 3.3.7 Redundant Entry: users are not asked to type the same information twice in one process.
- 3.3.8 Accessible Authentication (Minimum): logging in does not depend on a cognitive test such as remembering or transcribing a code, unless an alternative or help is offered.
For services under the European Accessibility Act, we also check the requirements of the Act's first annex that go beyond the page itself, such as information about the service, support services, and identification and payment methods.
For who is in scope, the microenterprise exemption, the accessibility statement and the transitional periods, see our European Accessibility Act guide.
What the audit covers
- Key user journeys. The tasks that matter for your business, such as account creation, search, product page, checkout, booking, login and contact. A journey that fails at one step fails completely, so we test end to end.
- Automated scan. A crawl of the site or the app's screens with automated tools, to find the repeated, mechanical issues across many pages.
- Manual testing. Keyboard only, screen readers (VoiceOver, TalkBack and NVDA), zoom to 200 % and 400 %, text spacing, reduced motion, high contrast and voice control.
- Content. Alternative text, headings, link text, plain language, captions and transcripts, error messages and documents such as PDFs that are part of the service.
- Components. Menus, dialogs, carousels, date pickers, file uploads, consent banners, chat widgets and payment forms, including third-party ones.
- Mobile apps. Native iOS and Android screens with the platform screen readers, dynamic type and touch target sizes.
What you get
- A summary for management: how accessible the service is today, the main risks and what fixing them involves.
- A ranked fix list: each issue with the page or screen, the element, the WCAG criterion, the effect on users, a severity rating and the recommended fix, ordered by impact on real tasks.
- Notes for your team: code-level guidance or examples for the most common fixes, so your team fixes the pattern once instead of page by page.
- Accessibility statement input: the facts you need for the information the European Accessibility Act asks service providers to publish.
- A retest after the fixes, so you know they work.
The failures we find most often
Every site is different, but the same problems come up in almost every audit, and most of them take little effort to fix once found. Form fields without labels, so a screen reader announces only "edit text". Error messages shown in red only, or placed far from the field they belong to. Buttons built from images or icons with no text alternative. Menus and dialogs that cannot be opened or closed with the keyboard, or that trap the focus inside them. Text over photos with too little contrast. Carousels that move on their own with no way to pause them. Product images whose alternative text is the file name. Videos without captions. Checkout steps that time out without warning. And on mobile, touch targets so small or close together that people hit the wrong one. Each of these blocks a real customer at a real step, which is why the fix list is ordered by the journeys they break.
Fixing, not just reporting
An audit report that nobody acts on helps no one. Because we also build and maintain websites and apps, we can fix the issues in your code: semantic HTML instead of clickable divs, labelled form fields, visible focus, correct ARIA where it is needed and removed where it hurts, accessible dialogs and menus, contrast within your brand colours, and captions. Many issues come from a few shared components, so fixing the design system or component library first repairs hundreds of pages at once. If your own team does the work, we review their changes and retest.
To keep it from slipping back, we add automated accessibility checks to the build pipeline and a short checklist for content editors. New features are tested before release, not after a complaint.
Audits for different systems
- Web shops: product filters, variant selection, basket, checkout and payment, where most failures cost sales directly. See also our online store service.
- Customer portals and intranets: login, dashboards, tables and forms used every day. See website portal development.
- Mobile apps: native screens, gestures and custom controls. See app development.
- Booking and self-service: calendars, time slot pickers and confirmations, common failure points. See booking system development.
- Business software: internal tools also have users with disabilities, and public procurement often requires accessibility.
What sets the cost of an accessibility audit
The cost of an accessibility audit follows the amount of manual testing it needs, not the number of pages. Five things set it: the number of distinct templates and components, since one tested product page stands for a thousand products; the number of key journeys, such as search, sign-up, booking or checkout; the platforms, because a website, an iOS app and an Android app are each tested on their own; the standard and depth, from WCAG 2.2 level AA to EN 301 549 with assistive technology testing; and whether fixes and a retest are included. A website accessibility audit quote that names the templates, journeys, platforms and standard can be compared with another; one that names a page count usually cannot.
How an accessibility audit runs
- Scope: we agree the site or app, the key journeys, the devices and assistive technologies, and the standard.
- Testing: automated scan plus manual testing of each journey and template.
- Report and walkthrough: the fix list, explained to your product and development team in one session.
- Fixes: by us, by your team, or shared.
- Retest and statement: confirm the fixes and prepare the accessibility information.
Yours to keep
The report, the fix list and any code we change belong to you. Fixes go into your own repository, and there is nothing to subscribe to. For a wider review of your code and security, see our security audit; for a site that needs a deeper rebuild, see website redesign. Our software requirements specification guide shows how to write accessibility into a new project from the start. See prices.
Questions we get
Does the European Accessibility Act apply to our company?
It applies to the products and services listed in Article 2 of Directive (EU) 2019/882 when they are offered to consumers in the EU from 28 June 2025. For most companies the relevant item is e-commerce services, which covers web shops and apps that sell to consumers, together with consumer banking, e-books, passenger transport websites and apps, and electronic communications. Microenterprises that provide services, defined in Article 3(23) as fewer than 10 persons and an annual turnover or balance sheet total of no more than 2 million euro, are exempt from the service requirements (Article 4(5)).
Is an automated accessibility checker enough?
No. Automated tools find a part of the problems, such as missing alternative text, low contrast and missing form labels, and they are useful for monitoring. Many failures need a person: whether alternative text is meaningful, whether the keyboard order makes sense, whether a screen reader user can complete the checkout. Our audit combines both.
Which standard do you audit against?
WCAG 2.2 at level AA, the current W3C recommendation, and the requirements that follow from the European Accessibility Act and the European standard EN 301 549. For apps we test with the screen readers and settings built into iOS and Android.
Do you also fix the problems?
Yes, if you want. The audit ends in a ranked fix list with the exact element, the failed criterion and the fix. We can make the fixes in your code, guide your own team through them, or both, and retest afterwards.
Do we need an accessibility statement?
The European Accessibility Act requires service providers to include information on how their service meets the accessibility requirements in their general terms and conditions or an equivalent document (Annex V). The audit gives you the facts for that statement, and we help you write it in plain language.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.