Chapter 4: Make text easy to understand
The introduction explains why accessible text must be understandable as well as perceptible, then previews the chapter’s topics.
After this chapter you will be able to
- Perceivable and understandable content. Explain why making web content perceptible is not enough: people must also be able to understand it without excessive effort.
- Clear and supportive wording. Explain why web app text should use simple, concise, empathetic language suited to its audience, including when that audience is highly technical.
- Unfamiliar words and abbreviations. Describe which kinds of words may need explanation and how to make their meaning clear when they first appear.
- Chunked and structured content. Explain how short paragraphs, headings, sections, and lists help people process longer text.
- Page and passage language markup. Describe where to set the lang attribute for a page and for content in another language, and identify the kind of language tags it accepts.
- Assistive technology language behavior. Explain how language markup affects speech and braille output, including what can happen when markup is missing and why correct markup still matters despite inconsistent support.
- Language selector state and semantics. Describe how the example selector makes its options accessible and identifies the currently selected localized page.
- Clear and deliberate language choice. Justify using text rather than flags for language choices and explain how the selector leaves the decision to switch languages with the user.
- Readable body font choices. Explain why decorative or thin-stroked fonts can be difficult to read as body text and how to make them more readable if used.
- Body text size and units. Explain why the section rejects 13px body text and recommends at least 1rem instead.
- Three content enlargement methods. Distinguish pinch-to-zoom, page zooming, and text scaling by what each enlarges and whether the layout reflows.
- Adaptable text and containers. Describe how font sizing, containers, and access to truncated text should accommodate browser or OS text scaling.
- Usability at increased size. State the 200% resizing expectation and describe what to check in layouts and controls when page zoom or text scaling increases content size.
- Relative sizing for adaptable content. Explain why the section recommends relative units for fonts, spacing, and containers instead of relying on fixed pixel values. Distinguish browser-computed CSS pixels from physical pixels and acknowledge that pixel-based text can still enlarge through page zoom.
- Browser default root scaling. Trace how a browser-default root font size and rem-sized text respond to a user's font-size setting, and contrast that with setting the root to 16px in the section's exercise.
- Single-direction content reflow. Explain how text and UI should adapt when users zoom, enlarge text, or use a small device: text wraps, and content remains readable and usable without being cut off or requiring horizontal scrolling.
- Reflow checks at narrow widths. Describe how to check reflow using 400% page zoom on a 1280px-wide screen or an unzoomed 320px viewport, and check both phone orientations for readable, usable content without loss or two-direction scrolling.
- Layout choices that break reflow. Explain how fixed or large minimum widths, non-wrapping text, fixed heights, and absolute positioning for core layout can prevent content from adapting and make it clipped or require two-direction scrolling.
- Readable user-controlled text spacing. Explain why people adjust letter, word, line, or paragraph spacing and why a site must remain readable when they override its defaults.
- Flexible layouts under spacing changes. Explain how a layout should accommodate increased text spacing without losing content or functionality, and how rigid constraints can cause cut-offs or overlaps.
- Limits of image-based text. Explain how embedding text in an image limits readers’ ability to resize, customize, and understand it through assistive technology.
- Real text for visual design. Describe why real text is preferable to a static graphic, including when a design calls for distinctive styling.
What it builds on
- (chapter intro) (chapter 3) · The preceding chapter’s focus on making content perceivable.
- Keep it POSH (Plain Old Semantic HTML) (chapter 2) · Use of semantic HTML to convey the purpose of content.
- The fundamental rule: semantic HTML reigns supreme (chapter 2) · HTML elements and attributes convey meaning to assistive technologies.
- Assistive technologies (chapter 2) · The role of assistive technologies such as screen readers and braille readers.
- Avoid using colors alone (chapter 3) · Meaning should not depend on a visual cue alone.
- Ensure sufficient contrast in text (chapter 3) · Understanding that text needs sufficient contrast.
- Complex images (chapter 3) · handling complex images
Section by section
Introduction
The introduction explains why accessible text must be understandable as well as perceptible, then previews the chapter’s topics.
- Perceivable and understandable content: Explain why making web content perceptible is not enough: people must also be able to understand it without excessive effort.
Why it matters: Visibility alone does not make content usable if reading it takes too much effort.
Key terms: perceive, understand
4.1 Write text for humans
This section explains how plain, supportive wording, explanations of unfamiliar terms, and well-structured text make web content easier for people to understand.
- Clear and supportive wording: Explain why web app text should use simple, concise, empathetic language suited to its audience, including when that audience is highly technical.
Why it matters: Clear, supportive wording lets readers spend less effort deciphering the text. - Unfamiliar words and abbreviations: Describe which kinds of words may need explanation and how to make their meaning clear when they first appear.
Why it matters: Explaining unfamiliar language prevents readers from having to guess what your content means. - Visible definitions and semantic markup: Explain how the improved example presents an abbreviation and a technical definition, and why an abbreviation's tooltip alone is insufficient.
Why it matters: Meaning should remain available to people who cannot access hover-dependent tooltips. - Chunked and structured content: Explain how short paragraphs, headings, sections, and lists help people process longer text.
Why it matters: A clear structure helps readers follow content without confronting a wall of text.
Key terms: simple, concise language, appropriate reading level, tone, jargon, figurative language, abbreviations, definitions, <abbr>, title attribute, <dfn>
4.2 Define language in single- and multilingual sites
This section explains how to mark up page and passage languages and build a language selector that assistive technology can interpret and users can control.
- Page and passage language markup: Describe where to set the lang attribute for a page and for content in another language, and identify the kind of language tags it accepts.
Why it matters: Language markup tells browsers and assistive technologies what language each piece of text uses. - Assistive technology language behavior: Explain how language markup affects speech and braille output, including what can happen when markup is missing and why correct markup still matters despite inconsistent support.
Why it matters: Correct markup can make text intelligible to assistive technology users even if a particular reader does not handle every case consistently. - Language selector state and semantics: Describe how the example selector makes its options accessible and identifies the currently selected localized page.
Why it matters: People need to find, understand, and operate the language options and recognize which version they are viewing. - Clear and deliberate language choice: Justify using text rather than flags for language choices and explain how the selector leaves the decision to switch languages with the user.
Why it matters: Clear labels and deliberate activation prevent confusing or unexpected changes of language.
Key terms: lang attribute, <html>, IETF BCP 47 language tag, regional variant, screen readers, speech synthesizers, braille translation software, pronunciation rules, language selector, lang
4.3 Apply font readability guidelines
This section shows how font choice, size, weight, contrast, and adaptable CSS affect the readability of body text.
- Readable body font choices: Explain why decorative or thin-stroked fonts can be difficult to read as body text and how to make them more readable if used.
Why it matters: A font that works for branding may make sustained reading difficult. - Body text size and units: Explain why the section rejects 13px body text and recommends at least 1rem instead.
Why it matters: Body text needs a readable starting size that can adapt to font-size settings. - User style override risks: Explain how overusing CSS !important can interfere with a reader’s custom styles.
Why it matters: Readers who depend on custom styles may lose the adjustments they need. - Accessibility-aware fonts and fallbacks: Describe the readability features of accessibility-aware web fonts and why fallback fonts are needed.
Why it matters: Distinct letters can ease reading, while fallbacks protect the experience when a web font is unavailable.
Key terms: body text, thin-stroked fonts, legibility, contrast, font-size, 13px, 1rem, relative rem unit, !important, user-defined styles
4.4 Enable content elasticity and adaptability
This section distinguishes three ways users enlarge content and explains how to keep text, layouts, and controls usable when they do.
- Three content enlargement methods: Distinguish pinch-to-zoom, page zooming, and text scaling by what each enlarges and whether the layout reflows.
Why it matters: The methods create different layout demands, even though each can make text appear larger. - Pinch zoom access and limits: Explain why a site should allow pinch-to-zoom but must not make it the only way to enlarge content, including how viewport settings can block it.
Why it matters: Allowing a gesture helps some users, but it cannot replace enlargement that preserves a usable layout. - Adaptable text and containers: Describe how font sizing, containers, and access to truncated text should accommodate browser or OS text scaling.
Why it matters: Enlarged text is only useful if its container and controls still reveal the complete message. - Usability at increased size: State the 200% resizing expectation and describe what to check in layouts and controls when page zoom or text scaling increases content size.
Why it matters: A page passes the practical test of enlargement only if people can still read it and use its controls.
Key terms: pinch-to-zoom, viewport scaling, page zooming, text scaling, layout reflow, user-scalable, maximum-scale, viewport, relative units, em
4.4.1 Adopt relative units
This section explains how relative CSS units help text and layouts respond to user font-size preferences and zoom.
- Relative sizing for adaptable content: Explain why the section recommends relative units for fonts, spacing, and containers instead of relying on fixed pixel values. Distinguish browser-computed CSS pixels from physical pixels and acknowledge that pixel-based text can still enlarge through page zoom.
Why it matters: Text needs room to grow without making content or functionality harder to access. - Browser default root scaling: Trace how a browser-default root font size and rem-sized text respond to a user's font-size setting, and contrast that with setting the root to 16px in the section's exercise.
Why it matters: Deferring the root size to the browser lets people who need larger text use their font-size preferences.
Key terms: relative units, em, rem, %, px, zoom, :root, font-size: 100%, font-size: 16px, browser default
4.4.2 Ensure content reflows properly
Explains how content should reflow at high zoom or in small viewports, how to check it, and why avoiding two-direction scrolling matters.
- Single-direction content reflow: Explain how text and UI should adapt when users zoom, enlarge text, or use a small device: text wraps, and content remains readable and usable without being cut off or requiring horizontal scrolling.
Why it matters: Good reflow keeps enlarged content readable without making users hunt across the page. - Reflow checks at narrow widths: Describe how to check reflow using 400% page zoom on a 1280px-wide screen or an unzoomed 320px viewport, and check both phone orientations for readable, usable content without loss or two-direction scrolling.
Why it matters: A layout that appears fine at normal size can fail when the available viewing space shrinks. - Layout choices that break reflow: Explain how fixed or large minimum widths, non-wrapping text, fixed heights, and absolute positioning for core layout can prevent content from adapting and make it clipped or require two-direction scrolling.
Why it matters: Recognizing these layout constraints helps explain why a page fails at high zoom or narrow widths. - Contained horizontal scrolling exceptions: Distinguish ordinary content from difficult-to-reflow, two-dimensional content such as tables, maps, or timelines; explain how unavoidable horizontal scrolling should stay within that element and remain discoverable and accessible.
Why it matters: The exception accommodates complex content without making the entire page difficult to navigate. - Vertical writing reflow direction: Explain how vertically oriented content should reflow: fit within the viewport height, extend horizontally, and avoid requiring scrolling in both directions.
Why it matters: The direction of acceptable scrolling depends on the writing mode, not on a universal ban on horizontal scrolling. - Barriers from failed reflow: Explain why two-direction scrolling and hidden content disproportionately affect people using high zoom or with motor or cognitive disabilities.
Why it matters: Reflow is about reducing effort and missed information, not just making a layout look tidy.
Key terms: reflow, text scaling, horizontal scrolling, 400% page zoom, 320px, device emulator, landscape and vertical orientations, fixed-width containers, min-width, non-wrapping text
4.4.3 Allow customizable text spacing
This section explains why users need customizable text spacing, how layouts can preserve content when spacing changes, and how to check a page for failures.
- Readable user-controlled text spacing: Explain why people adjust letter, word, line, or paragraph spacing and why a site must remain readable when they override its defaults.
Why it matters: Readers may need different spacing to use the same content comfortably. - Flexible layouts under spacing changes: Explain how a layout should accommodate increased text spacing without losing content or functionality, and how rigid constraints can cause cut-offs or overlaps.
Why it matters: A spacing override should not hide a link or make a control unusable. - Text spacing adaptation checks: Describe how to apply spacing overrides in browser developer tools and check whether page text and controls remain readable and reachable.
Why it matters: Testing with spacing changes reveals failures that a page’s default appearance may hide.
Key terms: text spacing, custom font settings, line height, paragraph spacing, word spacing, letter spacing, flexible CSS layouts, Flexbox, Grid, fixed heights
4.4.4 Liberate text embedded in images
This section explains why text should usually remain real, selectable text and how to handle the cases where text must appear in an image.
- Limits of image-based text: Explain how embedding text in an image limits readers’ ability to resize, customize, and understand it through assistive technology.
Why it matters: Readers need text that remains readable and meaningful when they change how a page is displayed or use a screen reader. - Real text for visual design: Describe why real text is preferable to a static graphic, including when a design calls for distinctive styling.
Why it matters: Keeping words as text can serve visual design while preserving readers’ control over their presentation. - Alternatives for necessary images: Distinguish the text alternatives needed for a rare image containing text, such as a logo, from those needed for an information-rich image.
Why it matters: An image’s brief description may identify it, but substantial information in the image must remain available as text.
Key terms: images of text, real, selectable text, alt tag, screen readers, real text, CSS, static graphic, alt attribute, full text alternative, complex images
4.5 Summary
Where this is used later
- Set page headings properly (chapter 5) · Builds on the value of meaningful headings when setting page headings.
- Build keyboard-friendly websites (chapter 5) · Keyboard-friendly navigation builds on the native keyboard behavior used for selector links.
- Layout (chapter 6) · The expectation that page content reflows rather than requiring two-dimensional scrolling.
- Links done right (chapter 5) · the limitations of text embedded in images
Concepts explained in this chapter
- relative unitA relative measurement unit specifies a size in relation to another value, such as a parent dimension, root size, or viewport.
- text scalingText scaling is enlargement or reduction of text through browser or operating-system text-size settings, with text growing along with its container.
- reflowReflow is the rearrangement of content so it remains usable when a viewport is narrowed or magnified.
- IETF BCP 47 language tagAn IETF BCP 47 language tag is a standardized identifier for a human language and optional regional or dialect variant.
- lang attributeThe lang attribute identifies the natural language of an HTML element's content.
- language selectorA language selector is an interface control that lets users choose the language in which a site or page is presented.
- spacingSpacing is the configurable separation between text characters, words, lines, or layout elements.
- zoomPage zooming is browser-controlled scaling of an entire web page that also causes its layout to reflow.
- maximum-scale attributeThe maximum-scale attribute of a viewport metadata declaration limits the maximum zoom factor available to users.
- pinch-to-zoomPinch-to-zoom is a multi-touch technique that magnifies a mobile device's viewport and its contents through spread and pinch gestures.
- resize textThe Resize Text success criterion is a WCAG requirement that text can be enlarged to at least 200 percent without loss of content or functionality.
- user-scalable attributeThe user-scalable attribute of a viewport metadata declaration controls whether users may zoom a web page.
- abbr elementThe abbr tag is an HTML element that marks an abbreviation or acronym and can associate it with an expanded form.
- chunkingChunking is the organization of information into smaller, meaningful units that can be processed as groups.
- dfn elementThe dfn tag is an HTML element that marks the term being defined within a definition.
- double negativeA double negative is a construction containing two negative expressions that can make the intended meaning difficult to interpret.
- reading levelReading level is an estimate of the educational reading ability required to understand written content.
- semantic markupSemantic HTML is the use of HTML elements whose names and structure convey the meaning, role, and organization of content.
- technical jargonTechnical jargon is specialized terminology used within a profession, industry, or technical domain.
- title attributeThe title attribute is an HTML global attribute that provides advisory text associated with an element.
- remA rem unit is a relative CSS length unit whose value is based on the root element's font size.
- absolute positioningAbsolute positioning places an element at coordinates relative to a containing block instead of participating in normal document flow.
- flexible CSS layoutA flexible CSS layout arranges content so its dimensions and positions can adapt to changing content or available space.
- line heightLine height is the vertical distance allocated to each line of text.
- readabilityReadability is the ease with which written content can be visually perceived and understood.
- contrastColor contrast is the visual difference between foreground content and its background, typically resulting from differences in luminance or color.
- alternative textAlternative text is a textual description or equivalent supplied for non-text content so its purpose and information can be conveyed without viewing it.
- image of textText rendered as pixels within an image rather than exposed as separately usable digital text.
- absolute unitA fixed unit is a CSS measurement unit whose value does not scale relative to another typographic or layout value.
- font-weightFont weight is a typographic setting controlling the thickness or boldness of text characters.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.
