The article discusses the challenges faced with Figma Sites in terms of web accessibility, emphasizing the lack of alerts for untagged elements or missing attributes prior to publication. Despite discovering an accessibility tool in the design section, the author finds that the actual implementation does not translate to improved accessibility in the live product since Figma uses generic <div> elements. The critique highlights a disconnect between Figma's aesthetic enhancements and the essential principles of inclusivity, raising concerns about the impact on web content generation.
I later discovered the Accessibility section hidden in the Design toolbar, offering options for adding tags, alt text, and ARIA labels to elements.
Counterintuitively, even with proper tags, Figma wraps all content in generic <div> elements, compromising the accessibility of basic content blocks.
Disregarding key aspects of web accessibility even in a beta product launch speaks volumes.
Figma continues to expand its AI capabilities - a juxtaposition that I find particularly amusing, granted that Figma Sites fails to meet the baseline of generating usable web content.
Collection
[
|
...
]