WCAG

Figma Sites automatically adds aria-label attributes everywhere, often duplicating visible content or mislabeling as alt text, causing WCAG 2.5.3 (Label in Name) failures. When accessibility tags are applied to headings, the duplicated aria-label makes content completely inaccessible to VoiceOver by grouping it incorrectly.

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 Sites has poor reading order and focus management—content blocks aren't accessibility-ready (e.g., images appear before headings in card layouts to screen readers). The tool provides no functionality for essential accessibility features like skip links or proper keyboard focus order.

Accessibility settings in Figma Sites are hidden by default and must be manually added to each layer. Additionally, there's no high-level view of applied accessibility tags—users must click into every layer individually to check. Component behavior, variables, and states differ between Figma Design and Sites.