A mobile screen can look balanced at its default text size and become difficult to use when the user enlarges text. Labels may disappear, buttons overlap, or a crucial confirmation move beyond reach. Readability settings belong in routine testing of the actual task.
Prioritize the information people need
Identify the labels, values, and actions that must remain understandable. Let important text wrap where appropriate, and avoid fixed-height containers that clip the final line. Keep a clear reading order when the layout changes.
Do not reduce the user's chosen text size to preserve a design. The interface should adapt around the content rather than forcing the person back to a less readable setting.
Test a complete action
Imagine a hypothetical booking app where the enlarged service name hides the appointment duration. A user may select a slot without seeing an important condition. Reviewing a static home screen would miss that problem; the test needs to include selection, review, and confirmation.
Check short and long real-world labels, errors, translated content where supported, and device orientations the product intends to serve. A generous layout for sample text may still fail with an actual customer name or service description.
Keep controls understandable
Make actions distinguishable without relying only on color or a small icon. Verify that enlarged text does not separate a label from the field it describes. Where content scrolls, ensure the user can still reach the primary action without an overlay covering it.
Use accessibility testing appropriate to the platforms involved, including assistive technology where the scope requires it. A larger-text check is useful but does not by itself establish full accessibility.
Start with the app's most important form. Increase text size, complete the task, and record each point where information becomes hidden or ambiguous. Fix those observed problems before treating the default-screen review as approval.

