Skip to main content
Accessibility.com, LLC
Category: Visual and Media Accessibility

Text Resizing

Also known as: Resize Text, Text Scaling, Font Scaling
Simply put

Text resizing is the ability to make on-screen text larger so it is easier to read, without breaking the layout or hiding any content or features. It helps people with low vision or reading difficulties adjust text to a comfortable size using their browser or device settings, rather than needing separate assistive technology.

Formal definition

Text resizing refers to enabling users to scale text without loss of content or functionality. Under WCAG 2.1 Success Criterion 1.4.4 Resize Text (Level AA, originally introduced in WCAG 2.0), text (except captions and images of text) must be resizable without assistive technology up to 200 percent without loss of content or functionality. This is distinct from page zoom; some practitioners use the term 'font scaling' to describe adjusting text size independently of overall page zoom. Meeting this criterion is commonly verified through manual testing, since automated tools detect only a portion of related issues.

Why it matters

Text resizing directly affects whether people with low vision, age-related vision changes, or reading difficulties can access content on a page. When text can be enlarged to a comfortable size, these users can read independently using built-in browser or device settings rather than relying on separate assistive technology. When resizing breaks the layout, clips content, or disables features, the practical result is that some users are locked out of information or functionality that everyone else can use.

Under WCAG 2.1 Success Criterion 1.4.4 Resize Text (Level AA, originally introduced in WCAG 2.0), text other than captions and images of text must be resizable up to 200 percent without loss of content or functionality. AA is the conformance level most commonly cited as a target in accessibility programs and in many settlements and agency guidance, so failing this criterion can contribute to both usability barriers and potential exposure to accessibility-related complaints. It is worth emphasizing that meeting a success criterion is not the same as guaranteeing a fully usable experience or legal immunity; this entry is not legal advice, and requirements evolve through regulation and case law.

Because layout problems from resizing often appear only when text is actually enlarged, these issues are easy to miss during ordinary development and are frequently caught only through deliberate testing. Automated tools detect only a portion of related issues, so overlooked resizing failures can persist in production and affect real users who depend on larger text every day.

Who it's relevant to

Accessibility Engineers and QA Testers
Those responsible for verifying conformance need to manually confirm that text can be enlarged up to 200 percent without loss of content or functionality, since automated tools detect only a portion of resizing-related issues. This includes checking for clipped text, overlapping elements, and controls that become unusable at larger sizes.
UX Designers and Front-End Developers
Designers and developers shape whether layouts adapt gracefully when text is scaled. Building flexible typography and layouts, and distinguishing font scaling from page zoom where relevant, helps ensure that enlarging text does not break the interface or hide features.
Compliance Officers and Legal Counsel
Those managing accessibility programs and risk should understand that Resize Text (SC 1.4.4) is a Level AA criterion, the level most commonly cited as a target. Meeting it supports accessibility goals but does not by itself guarantee legal safety; qualified legal counsel should be consulted on how evolving regulation and case law apply to a specific context.
Users with Low Vision or Reading Difficulties
The people most directly served by text resizing are those who benefit from larger text, including users with low vision, age-related vision changes, or reading difficulties, who can adjust text through built-in browser or device settings rather than depending on separate assistive technology.

Inside Text Resizing

Text Resizing
The ability for users to increase the size of text content, typically through browser zoom, browser text-size settings, or operating system controls, so that content remains readable without loss of information or functionality.
WCAG 1.4.4 Resize Text (Level AA)
A WCAG 2.0 success criterion, retained in later versions, which generally states that text should be resizable up to 200 percent without loss of content or functionality, and without requiring assistive technology to do so.
WCAG 1.4.10 Reflow (Level AA)
A success criterion added in WCAG 2.1 that addresses content reflowing to a single column at high zoom or narrow viewport widths, so that users do not have to scroll in two dimensions to read content.
WCAG 1.4.12 Text Spacing (Level AA)
A success criterion added in WCAG 2.1 that requires content to remain usable when users override line height, paragraph spacing, letter spacing, and word spacing, which is related to but distinct from resizing text size itself.
Browser Zoom vs. Text-Only Resizing
Browser zoom scales the entire page including images and layout, while text-only resizing changes only text size; both are common mechanisms users rely on, and content should generally accommodate them.
Relative Units
Sizing text and containers with relative units such as em, rem, or percentages, rather than fixed pixel values in ways that prevent scaling, so text can respond to user resizing preferences.

Common questions

Answers to the questions practitioners most commonly ask about Text Resizing.

Does zooming a browser to 200% satisfy the WCAG requirement for resizing text?
Not necessarily. WCAG 2.0 Success Criterion 1.4.4 (Resize Text), at Level AA, generally calls for text to be resizable up to 200% without loss of content or functionality, but it does not prescribe a single mechanism. Browser page zoom is one approach, and some users rely on it, but WCAG 1.4.4 focuses on the ability to enlarge text specifically rather than uniformly scaling the entire page. WCAG 2.1 added Success Criterion 1.4.10 (Reflow), also at Level AA, which addresses content presented without horizontal scrolling at equivalent scaling. Meeting these criteria commonly involves testing with both browser zoom and text-only sizing where the platform supports it, and confirming that no content is clipped, overlapped, or made non-functional.
If text resizes correctly, does that mean the page is accessible and legally compliant?
No. Supporting text resizing addresses specific WCAG success criteria but does not by itself make a page accessible to all users or guarantee legal compliance. Conformance with individual criteria is distinct from overall usability and from compliance under laws such as the ADA. Automated checks detect only a portion of potential issues, so manual review and testing with assistive technology are generally needed. Whether a given interface meets a legal obligation depends on the applicable authority and evolving case law and regulation; this entry is not legal advice, and organizations should consult qualified legal counsel for their specific situation.
Which WCAG success criteria are most relevant to text resizing?
The criterion most directly on point is WCAG 2.0 Success Criterion 1.4.4 (Resize Text) at Level AA, which generally addresses enlarging text up to 200% without loss of content or functionality. WCAG 2.1 introduced Success Criterion 1.4.10 (Reflow) at Level AA, concerning content reflowing without requiring horizontal scrolling at defined scaling, and Success Criterion 1.4.12 (Text Spacing) at Level AA, concerning adjustments to line, paragraph, letter, and word spacing. Teams often consider these criteria together when evaluating how content responds to enlargement.
How should text sizes be defined in CSS to support resizing?
Relative units such as em, rem, or percentages generally scale more predictably with user and browser text-size settings than fixed pixel values do in some contexts. Using relative units for font sizes, and for related spacing and container dimensions where practical, commonly helps text enlarge without being clipped or overlapping other content. The appropriate approach can vary by design system and platform, so results should be verified through testing rather than assumed from the unit choice alone.
What problems commonly appear when text is enlarged?
When text is scaled up, common issues include content being cut off within fixed-height containers, text overlapping adjacent elements, controls or navigation becoming hidden or unusable, and the introduction of horizontal scrolling. Content set in images of text may not resize cleanly. Reviewing layouts at increased scaling helps identify where these failures occur so they can be corrected.
How can text resizing be tested effectively?
Testing generally combines browser zoom, any available text-only sizing controls, and platform or operating-system text-size settings. Reviewers commonly enlarge content toward the 200% target and check that all text remains visible, readable, and functional, that no content is clipped or overlapped, and that horizontal scrolling is not introduced where reflow is expected. Because automated tools detect only a portion of relevant issues, manual review and testing with assistive technology are generally recommended alongside them.

Common misconceptions

Text resizing only matters for users who are fully blind.
Text resizing primarily benefits people with low vision and others who find larger text easier to read; users who are fully blind more commonly rely on screen readers. The success criterion is intended to help users adjust text without necessarily using assistive technology.
Supporting 200 percent zoom automatically satisfies all related WCAG requirements.
The 200 percent resize expectation in 1.4.4 is distinct from the Reflow criterion (1.4.10) and Text Spacing criterion (1.4.12) added in WCAG 2.1. Meeting one does not guarantee meeting the others, and each addresses different aspects of adaptable presentation.
If text resizes without visible breakage, the page is fully accessible and legally compliant.
Meeting a text-resizing success criterion is one part of conformance and does not guarantee an accessible experience for all users or immunity from legal claims. Manual review and testing with assistive technology remain necessary, and legal compliance depends on applicable law and current guidance.

Best practices

Verify that text can be resized up to at least 200 percent without loss of content or functionality, testing with browser zoom as commonly targeted by WCAG 1.4.4 (Level AA).
Use relative units such as em, rem, or percentages for text and containers so content responds to user resizing and browser settings rather than relying on fixed pixel sizes that resist scaling.
Test for reflow to confirm content adapts to narrow viewports and high zoom without forcing two-dimensional scrolling, consistent with WCAG 1.4.10 added in WCAG 2.1.
Confirm content remains usable when users apply increased text spacing (line height, paragraph, letter, and word spacing), consistent with WCAG 1.4.12 added in WCAG 2.1.
Combine automated checks with manual testing and testing using assistive technologies, since automated tools detect only a portion of resizing and layout issues.
Treat these steps as guidance rather than legal advice, and consult qualified legal counsel and current agency guidance regarding the specific requirements that apply to your organization.