Do your website cards and buttons still work when text is enlarged?

Define what the check establishes

The W3C Resize Text explanation addresses enlarging text up to 200 percent without losing content or functionality, subject to the criterion’s exceptions. Passing this check alone does not establish full accessibility conformance. It does provide a concrete acceptance question: can visitors still complete the same task after making text larger?

Example: a long product name

An illustrative manufacturer card uses the title “Stainless steel fixing for outdoor installations”. A title that occupies two lines at the default size needs more space when enlarged. A rigid card height may cause its price and detail link to overlap. Content-driven sizing, flexible spacing and fewer columns are possible responses. Shortening the product name until it loses meaning should not be the first remedy.

Do not assume both languages have equal length

A short Turkish label may be longer in English, and the reverse can happen too. An interface approved with only short examples may conceal its real content later. Include a long product title, a two-line action label, an error message and a long email address in design review. A fixed header or bottom bar that seems modest on desktop can consume much of the usable area when enlarged. Review these separately from body text.

Repeat the same task at a larger scale

First locate a product, read its details and reach the enquiry step at the default size. Then set browser zoom to 200 percent and repeat the task. Record clipped text, overlaps and unreachable controls. Use the keyboard to inspect where focus goes. If your browser supports text-only enlargement, test that separately as well. A small-screen review is not a substitute: each condition can reveal different problems.

Make the issue report reproducible

Instead of saying that a page “looks broken”, provide its address, browser, window size, zoom level, language and the text that was cut off. After the fix, repeat the task under the same conditions. Our typography guide covers heading and text hierarchy; this review checks whether that hierarchy survives enlargement. Include both visual evidence and task completion in website acceptance.

Prioritise issues by task impact. A clipped decorative heading and an unreachable submit control do not have the same consequence. First fix anything that prevents completion, then refine readability and spacing. For approval, repeat the original zoom level and language instead of requesting only a fresh desktop screenshot. That connects the fix to the condition in which the issue was reported.