Accessibility Audit for Web and Mobile Apps Under the EAA
Short answer
The European Accessibility Act requires many consumer-facing digital services in the EU, such as online shops, banking and ticketing apps, to be accessible. In practice, conformity is assessed against the harmonised standard EN 301 549, which builds on WCAG Level AA. An accessibility audit combines automated scans, keyboard and screen reader testing and a prioritised list of fixes.
Who the European Accessibility Act affects
The European Accessibility Act (EAA) is an EU directive implemented in national law in each member state. It applies to certain products and services offered to consumers, among them:
- e-commerce services, including online shops and booking platforms,
- consumer banking services,
- electronic communications services,
- e-books and dedicated reading software,
- websites, apps and e-ticketing for passenger transport,
- access to audiovisual media services.
Microenterprises providing services, meaning fewer than 10 employees and an annual turnover or balance sheet total of no more than 2 million euros, are exempt from the service requirements. Purely business-to-business services are generally outside the scope. Public sector bodies are covered by separate rules based on the EU Web Accessibility Directive. Whether your specific service falls under the EAA depends on national law and details of your offering. This page is general information, not legal advice; check your case with a lawyer.
What the audit measures
The practical benchmark is the harmonised standard EN 301 549, whose web and app requirements build on the Web Content Accessibility Guidelines (WCAG) at conformance level AA. WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. Even where EN 301 549 references an earlier WCAG version, testing against the current version is sensible, as the newer criteria largely address real mobile problems such as small touch targets and hidden focus.
A credible audit has three layers:
- Automated scanning with tools such as axe or Lighthouse. Fast, but it finds only part of the problems.
- Manual testing: keyboard-only navigation, screen readers (VoiceOver on iOS and macOS, TalkBack on Android, NVDA on Windows), zoom to 200 percent and larger system font sizes.
- Task-based checks: can a screen reader user register, find a product, pay and receive confirmation?
The most common issues in AI-built apps
Apps built with Lovable, Bolt, Claude Code and similar tools tend to share the same accessibility gaps, because the generated components optimise for looks:
| Issue | Typical fix |
|---|---|
| Icon buttons without a name | Add an accessible label, for example aria-label |
Clickable div elements | Use real button and link elements so keyboards and screen readers work |
| Removed focus outline | Restore a clearly visible focus style |
| Low contrast, grey on grey | At least 4.5:1 for normal text, 3:1 for large text and UI components |
| Form fields with placeholder only | Visible labels and error messages linked to the field |
| Dialogs and toasts not announced | Proper dialog semantics, focus management and live regions |
| Small touch targets | Follow platform guidance of about 44 points on iOS and 48 dp on Android |
Also check the lang attribute, alt text for meaningful images and whether layouts still work with large system fonts. In native and wrapped mobile apps, test with VoiceOver and TalkBack directly on devices.
From audit to fixes
Prioritise blockers first, meaning anything that prevents completing a core task. Then fix issues in shared components such as buttons, inputs and dialogs, since one fix there repairs many screens. Add automated accessibility checks to CI so regressions are caught, and give your coding agent explicit accessibility rules in its instruction file. Many services in scope must also publish information on how they meet the accessibility requirements, so keep your audit results documented.
How jocapps can help
UXreviewer.io delivers a UX report for your website, app or chatbot with commented screenshots, mockups and concrete improvement ideas from UX and psychology experts within 10 business days, a useful complement to a WCAG conformance check. OnlineAppCreator, our ISO-certified delivery team in Germany, implements fixes in web and mobile apps, including AI-built ones. See our prototype to production service or book a free 30-minute intro call via the meeting planner.
Frequently asked questions
Does the European Accessibility Act apply to my app?
It covers specific consumer-facing services such as e-commerce, banking, ticketing and e-books, with an exemption for service microenterprises. Whether your app is in scope depends on national law and your offering; ask a lawyer for a binding assessment.
Is an automated accessibility scan enough?
No. Automated tools find only part of the issues. Keyboard and screen reader testing on real devices are needed for a reliable picture.
Which WCAG level is required?
The harmonised standard EN 301 549 builds on WCAG Level AA for web content and apps, so AA is the practical target.
Are AI-built apps less accessible?
They often have recurring gaps such as unnamed icon buttons, clickable divs and missing focus styles. These are usually quick to fix in shared components once identified.
Guides on this topic
Related solutions
- Production readiness and auditsApp Performance Audit for Web and Mobile Apps
- Production readiness and auditsMaking a Bolt.new App Production-Ready
- Production readiness and auditsSecurity Review for Lovable and Supabase Apps
- Production readiness and auditsTaking a Replit App From Prototype to Production
Talk to us about your project
Honest advice on your idea, prototype or app.
- 30 minutes
- Free
- No obligation
