liveBook · Manning

Chapter 3: Make content easy to perceive

What you will learn in chapter 3 of Architecting Accessibility

Introduces perceivability as the principle that web content must be available in ways people with different sensory needs can receive and use.

After this chapter you will be able to

What it builds on

Section by section

Introduction

Introduces perceivability as the principle that web content must be available in ways people with different sensory needs can receive and use.

Key terms: perceivable, sensory channels, assistive technologies

3.1 Ensure sufficient contrast

This section explains why text and UI elements need sufficient contrast to remain visible and usable across different people and viewing conditions.

Key terms: sufficient contrast, low contrast, perceivable

3.1.1 Measuring contrast

The section explains how WCAG ratios and APCA measure contrast, how to interpret their results, and how to check contrast in practice.

Key terms: WCAG contrast ratio, relative luminance, foreground, background, Level AA, normal text, large text, non-text contrast, APCA, Lightness Contrast

3.1.2 Ensure sufficient contrast in text

This section explains where text contrast thresholds apply and why meeting them is only a starting point for readable text.

Key terms: minimum contrast ratios, text size, bold, inactive or disabled components, lower contrast, legibility, sufficient contrast, thin fonts, body text, visual fatigue

3.1.3 Ensure sufficient contrast in UI components and graphics

This section explains how sufficient contrast makes UI controls, their states, and meaningful graphics perceivable, and demonstrates how to check and improve a low-contrast form.

Key terms: non-text contrast, UI components, graphical objects, 3:1, APAC Lc 60, links, non-color visual cues, input field, placeholders, selected and unselected states

3.1.4 Ensure contrast across viewport sizes, zoom levels, and orientation

This section explains how responsive layout changes can reduce contrast and how to check and protect contrast across viewport sizes, zoom levels, and orientations.

Key terms: contrast-safe layouts, decorative backgrounds, solid-color overlays, responsive design, viewport widths, zoom levels, orientations, manual testing

3.1.5 Respect dark and light modes

The section explains why respecting light and dark preferences helps users and how to implement maintainable themes without sacrificing contrast.

Key terms: dark mode, color scheme, contrast, :root, var(), color-scheme, prefers-color-scheme, theme variables, design tokens, light-dark()

3.2 Avoid using colors alone

The section explains why color must not be the only way to convey meaning, shows alternatives for common UI elements, and describes how to check designs when colors are perceived differently.

Key terms: color alone, supporting cue, grayscale, validation states, programmatically associated error message, line styles, status, actions, decorative symbols, accessible name

3.3 Use images carefully

This section explains why accessible images must preserve meaningful information without making it harder for assistive-technology users to find.

Key terms: decorative images, accessibility tree, reading order, audio clutter, accessible names, alt attribute, alternative text, empty alt attribute

3.3.1 Decorative images

Explains why decorative images should be kept out of assistive technology output and how to do and verify that.

Key terms: decorative images, accessible names, audio clutter, CSS background-image, alt="", aria-hidden="true", inline SVG, alt attribute, role="none", role="presentation"

3.3.2 Simple informative images

This section explains how to write context-appropriate alternative text for simple informative images and why AI-generated text needs human review.

Key terms: simple informative images, alternative text, informative images, decorative, complex images, AI-generated alternative text, functional, automated accessibility testing tools

3.3.3 Functional images

This section explains how to give functional images and SVGs accessible names while hiding purely decorative or redundant graphics.

Key terms: functional images, alternative text, alt attribute, accessible name, aria-label, visible text, decorative, alt="", aria-hidden, assistive technologies

3.3.4 Complex images

This section explains how to make the information in complex images available through brief alt text and a structured text description.

Key terms: complex images, alt attribute, full equivalent information, semantic structure, full text description, <figure> element, figure captions, aria-describedby, longdesc, visible description

3.3.5 Interactive images (image maps)

Explains how image maps create clickable regions in an image and what makes those regions accessible.

Key terms: image map, <map>, <area>, <img>, usemap, alt attribute, meaningful alt text, keyboard accessible, href

3.4 Handle audio and video carefully

Accessible audio and video must not make information or functionality depend on one sensory channel, and users need some control over how the media behaves.

Key terms: single sensory channel, control

3.4.1 Do not force audio or video on people

This section explains why meaningful information in audio, video, and animation must also be available as accessible text.

Key terms: programmatically accessible text alternative, captions, transcripts, sensory channel

3.4.2 Media alternatives

This section explains how captions, transcripts, audio descriptions, and accessible media players make audio and video content available in alternative forms.

Key terms: captions, closed captions, open captions, speaker identification, meaningful non-speech sounds, WebVTT, <track>, time-coded text file, caption cues, basic transcript

3.4.3 Auto-playing audio

This section explains why auto-playing audio creates accessibility barriers and how to keep users in control of audio and video playback.

Key terms: auto-playing audio, screen reader announcements, pause, stop, mute, keyboard accessible, accessible names, auto-playing media, browser behavior, accessibility safeguard

3.4.4 Sound as feedback

This section explains how to make audio feedback accessible through visible and programmatically announced updates without overwhelming users with announcements.

Key terms: audio notifications, visible text message, programmatically determinable status update, ARIA live regions, role="status", aria-live="polite", role="alert", aria-live="assertive", audio clutter, critical, time-sensitive information

3.5 Summary

3.6 References

Where this is used later

Concepts explained in this chapter

← Chapter 2: People, technologies, and fundamental techniques Chapter 4: Make text easy to understand →

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.