Goal
Avoid using images of text when real text can be used.
Loading ...
Success Criterion · WCAG 1.4.5
If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for customizable or essential purposes.
Goal
Avoid using images of text when real text can be used.
What to do
Use actual text instead of text embedded in images, except when the presentation is essential or the user can customize it.
Why it matters
Real text can be resized, reflowed, translated, and read by assistive technologies; images of text cannot.
Success criterion
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for customizable images of text and essential images of text.
Intent
Benefits
Why it matters
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may not be able to read text that becomes blurry when zoomed because it is embedded in an image.
Screen readers may skip or poorly announce text that is part of an image.
Users cannot adjust typography preferences when content uses images of text.
Exception guidelines
Document the rationale for each exception and note which alternative support you provide.
The user can customize the text (font, size, color) in the rendered image.
Requirement
Customizable images of text may be used.
A particular presentation of text is essential to the information being conveyed (e.g., brand mark).
Requirement
Essential images of text may be used.
Whenever possible, render text as text, not as part of an image. Images of text (like banners or buttons with text burned into an image) reduce accessibility because users cannot reliably scale, reflow, translate, or select the text. Exceptions exist if the image of text is essential (like a logo) or customizable by the user.
Reference: All summaries and highlights originate from Understanding WCAG 1.4.5 and the W3C quick reference.
Examples
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Pass
A styled `<button>` with real text “Get started” using CSS.
Fail
A PNG button with “Get started” baked into the image.
Pass
Hero headline is `<h1>` text with CSS styling.
Fail
Headline is part of a background image with no text alternative.
Pass
Logo image is used as branding (essential) with appropriate alt text.
Fail
Navigation text labels are images of text used for styling reasons.
Evidence to keep
Capture artifacts for VPATs, procurement reviews, and regression testing.
Official resources
Keep these links handy when writing acceptance criteria or responding to audits.
Official W3C interpretation, techniques, and intent for Images of Text.
Filterable list of sufficient techniques and failures.
Using CSS to control visual presentation of text.
Separating information and structure from presentation to enable different presentations.
Failure due to using images of text without providing the same information as text.
Implementation checklist
Testing ideas
Related success criteria