iOS and Android, against EN 301 549. Screen by screen.
Guided checks for every screen, including the Chapter 11 requirements WCAG does not cover, a ticket for every failure, and a statement built from the results.
Apps are on the paid plan. Connecting your own coding agent, so it runs part of the audit inside AUDITSU, is in beta with a limited number of customers; a named reviewer checks every finding and signs the record.
Your app is where the regulator looks, and it is the part nobody has tested.
- The website was audited. The app, where most of your customers actually are, was not.
- WCAG alone does not answer for an app. EN 301 549 Chapter 11 adds requirements for software.
- A release goes out every fortnight, and the last audit was a document.
- Procurement asks for a statement covering the app, and yours covers the website.
- A French court has ordered a retailer to make both its website and its app fully accessible.
An app is audited screen by screen, by people, against the standard that actually covers it.
Check. Ticket. Statement. Record.
Screen by screen, on a device, against the standard that covers an app.
Check
Guided checks per screen for iOS and Android, including the Chapter 11 requirements WCAG does not cover.
Ticket
Every failure becomes a ticket carrying the screen, the standard, the severity and an owner.
Statement
Your statement covers the app and follows the results, rather than the website alone.
Record
Every verdict is recorded against the person who made it, and re-audits show what changed.
The app, screen by screen, on the record.
- Guided checks per screen for iOS and Android, tailored to the standards you are held to.
- EN 301 549 Chapter 11 requirements, including screen reader compatibility and platform accessibility services.
- A ticket for every failure, with the screen, the standard, the severity and an owner.
- An accessibility statement that covers the app, built from the results.
- Evidence packs for tenders and due diligence, on the paid plan.
- The managed option if you would rather we ran the first one.
Who this is for.
- Teams shipping a consumer app inside the European Accessibility Act’s scope.
- Medtech and public-sector suppliers whose buyers ask for the standard by name.
- Product teams who have fixed the website and know the app is next.
Not for
A scan of your app store listing. This is the product itself, on a device, screen by screen.
The rest of accessibility.
What people ask.
What does EN 301 549 ask of an app that WCAG does not?
What does EN 301 549 ask of an app that WCAG does not?
Chapter 11 adds requirements beyond WCAG for software, including VoiceOver and TalkBack compatibility, platform accessibility services, and inheriting the accessibility preferences set on the device.
Do you need our source code or a build?
Do you need our source code or a build?
No. You audit the app as your users meet it, on a phone. Nothing is installed in your app and no code access is required.
What does the coding-agent beta do?
What does the coding-agent beta do?
On the paid plan you can connect your own coding agent, and it runs part of the audit inside AUDITSU. It is in beta with a limited number of customers, and a named reviewer checks every finding and signs the record. Book a call if you would like to see it on your own product.
How many screens should we audit?
How many screens should we audit?
Start with the journeys a regulator or a buyer would ask about: onboarding, the core task and anything involving payment or identity. Checks that do not apply to your app are filtered out before you start.
Can you run the first one for us?
Can you run the first one for us?
Yes. The managed audit starts at £1,500, covers apps as well as websites, and lands in your own account.
What does it cost?
What does it cost?
Apps are on the paid plan. The plans and what each includes are on the pricing page.
Ready to put the app on the record?
Bring the app and the deadline to a 30-minute call, and we will tell you what it would take.