Accessibility of AI-built apps: three in four with serious violations
The most frequent finding in the AI App Radar DACH that can prevent a “Go”: serious violations of accessibility rules in the fully loaded page.
75% of the AI-built apps checked in a browser had at least one serious accessibility violation (75% (2,449 of 3,280)). The check ran automatically with axe-core on the fully loaded page; only violations of impact “serious” and “critical” were counted. Source: decivo AI App Radar DACH, run “2026-Q4-recall”, 3,728 apps with a DACH connection.
Key points
- 75% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (2,449 apps) had at least one serious accessibility violation in the fully loaded page (automated axe-core check, impact “serious” or “critical”).
- An automated check only finds part of all barriers. The true share is more likely higher than lower.
- Since 28 June 2025 the German Accessibility Strengthening Act applies to many consumer-facing offers.
The figure
- Serious accessibility violations in the fully loaded page
The base is the apps for which the check in a real browser ran.
The check runs on the page as a person sees it: after JavaScript has built it. That is decisive for AI-built apps, because their initial HTML is often almost empty.
Sentences to quote
You can use these sentences word for word. Each one names share, base and count. Please include the source line below.
75% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (2,449 apps) had at least one serious accessibility violation in the fully loaded page (automated axe-core check, impact “serious” or “critical”).
What is behind the figure
Serious means: some users cannot operate a function, or only with great effort. Typical cases are buttons without a name, input fields without a label, insufficient contrast and images without alternative text.
AI builders generate interfaces that look good. Whether a screen reader can read them out is not visible. That is exactly where the violations arise: in things that are right in the picture and missing in the code.
The German Accessibility Strengthening Act has applied since 28 June 2025 to, among other things, e-commerce services for consumers, such as shops and booking flows. Micro-enterprises providing services are exempt. Whether an app is covered depends on the individual case; the radar does not check that.
What the figures do not say
The radar measures what can be found. The 3,728 apps are not a random sample of all AI-built apps. The correct phrasing is “x% of the 3,728 discoverable AI-built apps with a DACH connection”, never “x% of all Lovable apps”.
The check runs from the outside and without logging in: what the page ships and what a browser observes while loading. The radar does not see database rules, roles or anything behind the login. A share says for how many apps a rule fired. It does not say whether the finding holds in each case, and it is not legal advice.
The report deliberately does not cite everything. At the time, for fonts, trackers, contacted services and findings in shipped code a mere mention also counted, for example in an embedded third-party script. Since methodology 2026.43 only what the page demonstrably loads or contains in its own code counts; exception: if the page ships no code of its own, the rules for database write calls and role comparisons check an embedded third-party script. These shares may be lower when measured again. Those shares are in the dataset, but not in this text.
The figures are decivo's own survey. decivo itself offers to fix such findings. They have not been independently verified so far; the dataset is open for that purpose.
Automated tools detect what can be decided by machine. Whether keyboard operation makes sense or an alternative text really describes the image is something only a person checks. An app without hits is therefore not automatically accessible.
The basis is the run “2026-Q4-recall”, closed on 8 November 2026. Across all 14 runs since September 2026 the radar has scanned 4,402 apps; the report uses the single run because it has one methodology and a fixed address.
Check your own app
Install the free browser extension axe DevTools, open your app and start the check on the fully loaded page. Begin with the violations of impact “critical”: names for buttons, labels for fields, contrast.
The free scan also checks with axe-core and names the most frequent violations. The other figures are in the AI App Report DACH 2026.
Sources
Every share comes from the radar run named below. Its fixed address shows exactly these figures; the legal sources are the statutes themselves.
- decivo: AI App Radar DACH, run “2026-Q4-recall”, 3,728 apps, methodology 2026.37 (CC BY 4.0)
- decivo: raw figures of the run as JSON (CC BY 4.0)
- decivo: AI App Report DACH 2026, November 2026 edition
- Barrierefreiheitsstärkungsgesetz, BFSG (gesetze-im-internet.de)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- Deque: axe-core (GitHub)
Whether your app is part of these shares, the free scan shows in a few minutes: from the outside, without access, with evidence for each finding.
Check your app for freeQuestions about accessibility
How many AI-built apps are not accessible?
75% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (2,449 apps) had at least one serious accessibility violation in the fully loaded page (automated axe-core check, impact “serious” or “critical”).
What was used for the check?
With axe-core, an open testing library, on the fully loaded page in a real browser. Violations of impact “serious” and “critical” were counted.
Is an app without hits accessible?
Not automatically. An automated check only finds part of the barriers; a test with keyboard and screen reader shows the rest.
Related articles
- AI code quality
Privacy in AI-built apps: radar figures 2026
Trackers before consent, cookies without agreement, missing legal notice: what the AI App Radar DACH measured in AI-built apps, with count, base and sentences to quote.
- AI code quality
AI-built apps in Germany and Switzerland compared
How many AI-built apps pass the scan without an urgent finding? The verdicts of the AI App Radar DACH, split by country and by builder.
- Vibe Code Rescue
Lovable DPA & GDPR: Plans, Sub-processors, Data Location
Lovable ties its DPA to Business and Enterprise, Lovable Cloud stores data in the chosen region — AI requests not. How Supabase, Base44 and Bolt differ, which obligations your app has itself (legal notice, Art. 13, § 25 TDDDG, AI Act Art. 50, BFSG) a 12-point checklist and our own data from 454 AI-built apps in the DACH region.
Where does your app stand by comparison?
The decivo Scan checks your app from the outside, with the rules as they stand today, and names every finding with evidence.
30 minutes, free. You talk to us directly.