Figma Introduces Inclusive Component Variants and Pronoun Fields for Design Systems

Design · 4 min read

Inclusive Component Variants let teams create components that include built-in accessibility and inclusion states — for example, components with contextual microcopy for gendered language, locale-sensitive date formats, or optional privacy-preserving display modes. Designers can flag variant groups as "inclusion critical," which surfaces them in accessibility checkers and developer handoffs.

The new Pronoun field in user profile components provides a standardized way to represent preferred pronouns without hardcoding label patterns. When included in a design system file, the field links to recommended UX treatments — such as optional display, tooltip explanations, and privacy defaults — and toggles test fixtures for localization that avoids misgendering in automated tests.

Figma also updated its component analytics to report usage of inclusive variants across files and teams. Early reports indicate that when inclusive options are visible in the component palette, adoption rises significantly because designers no longer have to invent ad-hoc solutions for identity display. System maintainers can now push variant updates and track downstream adoption through Figma's libraries interface.