Figma Sites exports only generic divs, preventing semantic HTML and accessibility

9/10 Critical

Figma Sites generates only `<div>` elements without semantic HTML, making it impossible to create accessible websites that comply with WCAG standards. This poses litigation risk for businesses and prevents proper semantic structure required for screen readers and keyboard navigation.

Figma SitesHTMLWCAG
Category
compatibility
Workaround
none
Stage
build
Freshness
emerging
Scope
single_lib
Upstream
open
Recurring
No
Buyer Type
team
Maintainer
slow

Sources

Collection History

Query: “What are the most common pain points with Figma for developers in 2025?”4/9/2026

if the sites are going to be only be divs, it is essentially impossible to release accessible websites with it. Meaning most businesses globally can't use it without risking litigation... Everything defaults to a <div>. Why can't we utilise the purpose of some of the Blocks to add some basic semantics?

Created: 4/9/2026Updated: 4/9/2026