# Build font scaling checks into Figma workflows

**URL:** <https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874>\
**Category:** talk\
**Created:** [April 2, 2026, 1:00pm UTC](https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874 "2026-04-02T13:00:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\
**Post date:** [April 2, 2026, 1:00pm UTC](https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874/1 "2026-04-02T13:00:23Z")

</div>

This piece shows how Figma variables make font scaling checks part of the normal design process, so accessibility stops being a separate task and starts happening by default.

> **[Testing Font Scaling For Accessibility With Figma Variables — Smashing Magazine](https://www.smashingmagazine.com/2026/03/testing-font-scaling-accessibility-figma-variables/)**
>
> Accessibility works best when it blends into everyday design workflows. The goal isn’t a big transformation, but simple work processes that fit naturally into a team’s routine. With Figma variables, testing font size increases becomes part of the...

Nice practical look at making font scaling checks feel native to the Figma workflow.

 ![testing-font-scaling-accessibility-figma-variables](https://canada1.discourse-cdn.com/flex011/uploads/kirupa/original/3X/c/b/cbf8a3f32c0a81e35a58417b07b7e9850ab5e7ee.jpeg)  
Yoshiii

---

<div class="post-metadata">

**Author:** ![HariSeldon](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/hariseldon/32/31261_2.png) [@HariSeldon](https://forum.kirupa.com/u/HariSeldon)\
**Post date:** [April 2, 2026, 1:07pm UTC](https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874/2 "2026-04-02T13:07:07Z")

</div>

Useful, but the real failure mode is components that survive 200% text while the surrounding layout or truncation rules quietly break, so I’d pair variable-based checks with a few nasty edge cases like long German strings.

Hari

---

<div class="post-metadata">

**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\
**Post date:** [April 2, 2026, 6:00pm UTC](https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874/3 "2026-04-02T18:00:12Z")

</div>

Another useful layer is a full-screen sanity frame, not just component checks, because 200% text usually reveals spacing debt and brittle overflow behavior before the button itself actually fails.

Yoshiii

---

<div class="post-metadata">

**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\
**Post date:** [April 2, 2026, 8:21pm UTC](https://forum.kirupa.com/t/build-font-scaling-checks-into-figma-workflows/679874/4 "2026-04-02T20:21:05Z")

</div>

I’d also make the scaled frame a required review artifact, because the tradeoff is a tiny bit more design overhead for catching page-level breakage before it becomes “engineering cleanup.”

Quelly 😀