04 Figma Release Notes · September 3, 2026 ([figma.com](https://www.figma.com/release-notes/?utm_source=openai))

Small system controls can unlock cleaner visual governance

Figma added scalable opacity controls for variables, aliases, disabled states, overlays, and scrims without detaching colour relationships.

Define opacity as a variable rather than a manual adjustment.

Name and scope it for specific interface contexts such as disabled states or scrims.

Test the variable across themes, accessibility modes, and component states.

Document when opacity should be used—and when contrast requires a different colour.

Review the system at scale.

Look for places where a tiny control change improves consistency across dozens of surfaces.

The Story

Figma’s September 3 release is a quiet but useful example of system maturity: opacity can now be managed at scale while keeping colour variables linked. ([figma.com](https://www.figma.com/release-notes/?utm_source=openai))

These details rarely make a launch headline, yet they shape how reliably a system behaves across states, themes, and edge cases. Good systems reduce the number of tiny decisions a team has to remake. ([figma.com](https://www.figma.com/release-notes/?utm_source=openai))

The Studio Wensday takeaway is to keep auditing the “small” variables. Consistency is often won through controls that feel almost invisible in the authoring tool.

Studio Wensday Angle

System quality is built from precise, repeatable decisions.