Lovable's AI built a 100% accessible site – or did it?
Lovable's AI claims to have built a 100% accessible website, but real-world testing reveals significant issues. A screen reader user encountered problems such as content being read from behind menus and interruptions from automated security features. These challenges highlight the gap between theoretical accessibility scores and practical user experiences.
- ▪The site was built using Lovable's AI by an individual during commutes.
- ▪It received a perfect accessibility score from Lovable's Speed tool, which runs Axe.
- ▪Real-life testing showed that users faced issues like ghosting effects and focus management problems.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Axess Lab |
| Canonical URL | https://axesslab.com/lovable/ |
| Publication time | Thu, 21 May 2026 12:42:57 +0000 |
| Retrieval time | 2026-05-21T12:51:11.071Z |
| Last seen | 2026-05-21T12:51:11.071Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | oSVeDdrohdIh |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Lovable’s AI built a 100% accessible site – or did it? Published 13 May 2026, by Hampus Sethfors We wanted to get an indication of how accessible AI-built sites are at the moment. So I let my colleague Daniel try out a site built with Lovable, using the screen reader on his iPhone. And we recorded it all so you can come along for the ride! Background about the site First off: the way the site was built was pretty mind blowing to me. A friend of mine, an AI-enthusiast, built it only using his smartphone during bus rides to and from work. The fact that you can now build a functional, high-fidelity site into existence while commuting is pretty cool. And you could argue that this is a form of accessibility, making it possible for many more people to build sites and apps.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Axess Lab.
Discussion
0 commentsMore from Axess Lab
