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, at mandatory AA compliance level, requires interfaces to support text scaling up to 200% without loss of content or functionality. Most design processes ignore this until it breaks something. This article is about fixing that before it breaks.
The core problem is control, or the lack of it. Designers cannot dictate how users interact with an interface. Screen readers, contrast overrides, and font scaling all transform the visual design in ways the designer never approved. The article argues this is not a failure state. It is the intended outcome of accessible design. Blocking these assistive technologies is not a design decision. It is a compliance violation with legal consequences. The piece also introduces AccessibilityOps, a framework for embedding accessibility into team workflows without restructuring how those teams operate.
What makes this worth reading in full is not the compliance checklist. It is the Figma Variables methodology for testing font scaling during the design phase, before anything reaches a developer. The article walks through how to simulate 120%, 140%, and 200% text scaling directly inside Figma, exposing layout failures early. If your team still treats font scaling as an edge case, this piece will reframe that assumption with specific tooling and a repeatable process.
[READ ORIGINAL →]