Running Lighthouse's Accessibility audit against real, published Framer sites turns up the same handful of failures again and again — not because the designers did anything wrong, but because these are structural gaps in how Framer's static export generates markup.
1. No lang attribute on <html>
Framer's exported HTML never sets <html lang="...">. Screen readers use this attribute to pick the correct pronunciation engine — without it, assistive technology has to guess, and often guesses wrong for non-English site content. This is a single missing attribute, and it's on essentially every Framer export we've checked.
2. Iframe embeds with no title
Video embeds (Vimeo, YouTube), maps, and other iframe-based content ship as bare <iframe src="..."> with no accessible label. A screen reader announces an untitled iframe by reading its raw src URL — not useful, and easily fixed with a single descriptive title attribute per embed type.
3. No main landmark
Screen reader users rely on landmark navigation (main, nav, header, footer) to jump directly to a page's primary content instead of tabbing through every element sequentially. Framer's markup wraps the whole page in a single, un-landmarked container — meaningful content and chrome are structurally indistinguishable to assistive tech.
4. Icon-only links with zero accessible name
Logo links and social icon links are commonly built as an anchor wrapping a decorative SVG marked aria-hidden="true" — correct for the icon itself, since decorative graphics shouldn't be announced, but it leaves the link with no name at all. A screen reader user tabbing to a site's logo link hears nothing describing where it goes.
Why this matters beyond compliance
Accessibility issues are also, mechanically, Lighthouse score deductions — meaning they affect the same audit that factors into how a site is perceived (and in some jurisdictions, legal exposure) independent of any moral argument for fixing them. In our 10-template test, fixing these four things alone lifted every single site's Accessibility score, with zero visual change to the page.
The fix is mechanical, not manual
None of these four issues require a designer to change anything about how a site looks — they're all invisible, structural additions: a lang attribute, a title on iframes, a landmark role, and an inferred label on icon links. Our Next.js and HTML converters apply all four automatically during conversion, alongside the rest of the SEO and performance pass — worth checking your own exported site's before/after Accessibility score via our PageSpeed comparison tool.