Resize Text and the Lessons It Teaches on Conformance and Techniques

A new piece published on mn.gov, "Resize Text and lessons on conformance and techniques," turns a single accessibility requirement into a working lesson on how the Web Content Accessibility Guidelines actually function.

The subject is text resizing — the ability of users to scale page text without breaking layout or losing content. Under WCAG 2.1, this expectation lives in Success Criterion 1.4.4, Resize Text, which calls for text to be resizable up to 200 percent without loss of content or functionality. It is one of the criteria practitioners most often misread, because people tend to confuse the requirement itself with the specific coding habits used to meet it.

That distinction — conformance versus technique — is the piece's real argument.

What is the difference between conformance and a technique?

Conformance, in WCAG terms, is a claim about the result. A page either allows text to scale to 200 percent or it does not; the success criterion defines the outcome, not the method.

Techniques are the documented ways of getting there. The W3C publishes techniques such as using relative units for font sizes, and these are advisory. Follow one and you are likely to conform. Skip one and you may still conform, provided the measurable outcome holds when tested.

The trap, as accessibility writers have long noted, is treating a technique as the rule. A team might mandate relative units everywhere, believe it is compliant, and still ship pages where resized text gets clipped or overlaps — a conformance failure hidden behind a satisfied technique.

Why does this matter for public-sector sites?

For a state domain like mn.gov, the stakes are concrete. Government services — forms, notices, benefit portals — carry information people cannot afford to lose. A low-vision user scaling text to 200 percent on a benefits page is not making an aesthetic choice; they are reading the only version of the page available to them.

The resize-text lesson generalizes. Every WCAG criterion pairs a testable claim about users' experience with a toolbox of implementation habits, and audits that check only the habits produce false confidence. The reliable method is the reverse: test the outcome — resize the text, use the page — and only then ask which techniques got you there.

That inversion, from checklist to observable behavior, is where the piece locates the broader lesson for designers and developers building to WCAG 2.1 today.