Does your Flutter app meet the European Accessibility Act?
An EN 301 549 audit that says what fails, in which file and on which line — and a signed report your lawyer can file. €690, 5 working days. There is no EAA certificate, and we say so.
€690 · 5 working days · with the signed report €1,080
For your lawyer
What you can show your lawyer
Two documents. The audit report lists every finding, the WCAG criterion and EN 301 549 clause it breaks, and the file and line it comes from. The signed conformance report goes through every criterion and states whether the app meets it, fails it, or was not checked. Neither is a certificate or a guarantee against a fine, and the next paragraphs say why.
There is no EAA certificate, and nobody can sell you one
No body in the EU is accredited to certify conformance with the European Accessibility Act. What exists is an audit report and an accessibility statement, and anyone offering you certification is selling you a document with no standing. Ours says what was tested, what was found, and what was not looked at.
Automated checking finds a minority of real accessibility problems. It is good at what it covers and silent about the rest, which is why every report we write marks each criterion as not satisfied, no automated violation, or not checked — and why the third of those is written down rather than left out.
A clean result is not a statement of conformance. It means nothing we checked was found to be wrong.
Specimen
Sample report: Wonderous — 33 defects, each with a file and a line
Rather than describe the output, here is a complete one. We audited Wonderous, the open-source app Flutter is showcased with — a careful, well-built application by people who know the framework.
| Requirement | What it asks | Defects |
|---|---|---|
WCAG 1.4.3 | Contrast (Minimum) | 17 |
WCAG 2.1.1 | Keyboard | 4 |
WCAG 2.5.8 | Target Size (Minimum) | 3 |
Platform guidance | Touch target size | 2 |
WCAG 4.1.2 | Name, Role, Value | 3 |
WCAG 1.4.4 | Resize Text | 2 |
WCAG 1.3.2 | Meaningful Sequence | 1 |
WCAG 1.4.11 | Non-text Contrast | 1 |
WCAG 2.4.7 | Focus Visible | none found |
WCAG 1.4.10 | Reflow | none found |
33 places in the code · 161 occurrences · 21 checks. Every one carries a file and a line, so the fix list is a work queue rather than an investigation.
Free tools
What the free tools find, and what they leave to you
Xcode's accessibility audit and Google Play's pre-launch report are free, and both see a Flutter app. Run them — they find real problems. This is what they leave to you.
| Xcode audit | Play pre-launch report | checkApp | |
|---|---|---|---|
| Sees a Flutter app | Yes | Yes | Yes |
| Price | Free | Free | From €690 |
| Platforms | iOS | Android | Both, in one report |
| Names the Dart file and line | No | No | Yes |
| Separates what EN 301 549 requires from platform advice | No | No | Yes |
| A person completes the common tasks with a screen reader | No | No | Yes |
| Which App Store accessibility labels you can claim | No | No | Yes |
| A signed document for a regulator or a client | No | No | Yes |
Both report what the platform sees on screen, not where in your code it comes from, and both measure against the platform's own guidance rather than the law. That gap is the work.
What the accessibility audit checks
- Controls a screen reader announces as unnamed
- Text and icons below the contrast the standard requires, measured from the painted frame rather than from the declared colour
- Tap targets under the platform minimum
- Reading order that does not match what is on screen
- Text at 200% that gets cut off, and layouts that break when it does
- Animation that keeps moving after someone asks it to stop
- Controls that look identical whether or not they have focus
- Password and code fields that block paste, so a password manager cannot help
- Controls that answer a tap but cannot be reached from a keyboard or a switch
- A button showing one word and named another, so voice control does not answer to what people see
- Form fields labelled only by a hint that disappears as you type, and fields for an email, phone or password that do not say so to autofill
- An app held in portrait or landscape, with the line of code that holds it
The standards and store rules we audit against
- Directive (EU) 2019/882
- European Accessibility Act — applies since 28 June 2025
- EN 301 549 v4.1.1
- ETSI, 2 September 2026 — points at WCAG 2.2 level AA
- EN 301 549 — European Accessibility Act
- Market surveillance, fines · 28 Jun 2025
Prices
Fixed prices, published. From €190.
EN 301 549, the standard the European Accessibility Act points at. Automated checks plus a screen-reader pass by a person, on both platforms, and which of Apple's accessibility labels you can honestly claim.
The same, for a product with a real surface area.
The signed document: every criterion, its clause number, where the product stands, and what was and was not checked. Added to any audit above.
Within 90 days of the original. Says what closed, what did not, and what the changes introduced.
A year on, your app has moved and so have the requirements. The same audit again, at 30% off, within 12 months of the last one.
EAA package: audit of up to 10 screens and the signed EN 301 549 report — €1,080.
One surcharge, and it is avoidable. If you can only give us a TestFlight build, the iOS accessibility pass has to be done entirely by hand and costs 60% more. A simulator build — flutter build ios --simulator, one command — avoids it.
Prices are reviewed every January.
Send a build. Get a report by email.
| What you send | Store checks | Accessibility |
|---|---|---|
.apk — Android | Full | Full |
.app — iOS simulator build | Full | Full |
.ipa — iOS device build | Full | Not possible |
| TestFlight invitation | Full | By hand, +60% |
FAQ
Does the European Accessibility Act apply to my app?
It has applied since June 2025 to consumer-facing products and services sold in the EU — e-commerce, banking, transport, e-books and telecoms among them. Businesses under 10 staff and €2M turnover providing services are outside it. If you are not sure which side you are on, that is a consultation, not an audit.
What are Apple's accessibility labels, and do I need them?
An App Store listing can now declare which accessibility features the app supports — VoiceOver, Voice Control, Larger Text, Dark Interface, Differentiate Without Color Alone, Sufficient Contrast, Reduced Motion, Captions and Audio Descriptions. They are optional today and Apple has set no date. But before a feature is declared, Apple asks that people can complete all of the app's common tasks using only that feature, and leaves defining the common tasks to you. We name them, walk them with each feature, and tell you which labels you can claim and what stands in the way of the rest.
Can you audit an app that is not Flutter?
The store checks work on any iOS or Android build. The accessibility checks are automated for Flutter and done by hand otherwise — ask, and we will quote honestly.
Get an audit
Email a build. Get a fixed price and a date.
Write to hello@checkapp.dev with the build, or a link to it, and one line on what you need: an accessibility audit, a store check, or both. You will get a fixed price and a date back the same working day.