Interfaces that ignore Dynamic Type lose low-vision and older users

What it is

Locking an interface to default type writes a reading threshold into the product. Low-vision users and many older adults have already enlarged type at the system level. In an app that does not follow, they are not “a little inconvenienced.” They cannot read the button, cannot see the price, cannot finish. Dynamic Type dropout names that departure, and how fast it happens — not a politeness slogan, an observable walk-away.

Why it happens

System-level enlargement is a cost those users have already paid: they tuned the whole device and expect every app to catch. An app that paints in frozen points voids that setting, and there is usually no second path “inside this app.” Unreadable means undoable; undoable means switching to something readable, and switching is cheap on a phone. Dropout clusters on steps that are decisions-by-reading: a dose instruction, a payment confirm, a transit time. A team with typical vision, sitting at default size, marks those steps as passed, because they were never the people locked out. Ignoring Dynamic Type is not a skipped typesetting nicety. It is blocking a channel the system already opened.

Where it stops holding

Specialist tools, control-room walls, and mostly-graphic screens with almost no copy have a smaller reading population; dropout is not counted on that ledger. In-world game lettering is sometimes part of the scene, and enlarging it would break composition — but menus, captions, and shops should still follow system type, or dropout happens at the menu, not in the level. An app with its own type control that actually reaches near the system maximum is not “ignoring”; that is another channel, if it works. Calling three in-app sizes “our setting” still fails if those three sit below the system accessibility maximum.

Applying it

• Do not freeze body copy and primary buttons in points that ignore system type. Catching the system channel is cheaper than a second, incomplete type control in Settings.
• Compare completion on these screens inside the subset of people whose system type is large. If analytics cannot see that subset, log the type bucket before arguing that dropout is imaginary.
• Walk payment or an appointment-booking flow with someone who already lives at the system maximum. If they cannot finish, a pass at default size is not a claim that the product is readable.

Related

• Same group: F4.16.1 Scale testing must include the system’s largest type bucket, not only the usual range · F4.16.2 Icon-plus-label controls must keep their alignment after type scales · F4.16.3 Large type may be on together with other assistive settings
• Nearby: F4.09 Dynamic Type · A11.03 Older adults’ interaction · J2.02 Text resize
• Search terms: Dynamic Type · low vision · older adults dropout