26% of Android and iOS users already increase their default font size, according to APPT data from February 2026. That is one in four people. WCAG 2.2 Success Criterion 1.4.4 requires text to scale up to 200% without loss of content or functionality, and that criterion sits at AA compliance level, meaning it is legally mandatory in most jurisdictions. If your design breaks at double font size, your product is non-compliant and your company is exposed.
The article's real value is not the compliance reminder. It is the framing around what the author calls AccessibilityOps: embedding accessibility into team workflows as process, not as a separate workstream. Designers do not control how users interact with their interfaces. Assistive technologies, font scaling, contrast overrides, and screen readers all transform the visual output. The piece argues clearly that blocking or ignoring these transformations is a design failure, not a user error. It also makes the case that you do not need to build font-size controls into your UI, because devices already provide them natively, and adding redundant controls creates complexity without benefit.
The full article walks through how to test font scaling using Figma Variables, which is the practical payoff buried past the editorial setup. If you work in product design and have not yet built responsive type scaling into your Figma process, the methodology here is specific and replicable. Read it for the implementation detail, not the accessibility sermon.
[READ ORIGINAL →]