Chapter 3: Make content easy to perceive
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
- Content perceivability across contexts. Explain why content must be perceivable across sensory channels, contexts of use, devices, browsers, and assistive technologies, rather than requiring people to use separate experiences.
- Sufficient contrast and legibility. Explain that sufficient contrast means text and UI elements stand out against their backgrounds so people can see, read, and use them. Describe why low contrast can make content difficult or impossible to read, especially under challenging viewing conditions or for people with vision impairments.
- WCAG contrast ratio model. Explain that WCAG calculates contrast from the relative luminance of foreground and background colors, producing a ratio from 1:1 to 21:1.
- Level AA contrast thresholds. State the main WCAG Level AA minimums: 4.5:1 for normal text and 3:1 for large text and meaningful non-text visuals, including UI components and focus indicators. Explain that larger text can remain visible at a lower ratio.
- APCA perceived contrast model. Describe how APCA reports perceived contrast as a Lightness Contrast (Lc) value rather than a WCAG ratio, accounting for text/background polarity and typography. Explain why a WCAG-passing combination can still be difficult to read.
- Conformance versus design guidance. Distinguish the roles of WCAG ratios and APCA: use the governing WCAG-based standard for conformance and APCA as supplementary guidance for design decisions.
- Foreground background checking steps. Apply the section’s basic contrast-checking workflow: choose an element, obtain its foreground and directly underlying background colors, enter both into a checker, and compare the result with the relevant threshold.
- Text contrast thresholds. Explain that WCAG minimum contrast ratios depend on text size and whether it is bold, and that the thresholds apply to text in interactive components and images as well as ordinary text.
- Contrast beyond minimum ratios. Explain why passing a minimum contrast ratio does not guarantee readable text and why maximum contrast is not always the aim.
- Non-text contrast baseline. Explain why contrast requirements apply to interactive components and meaningful graphics, not just text, and state the contrast values recommended in this section.
- Control boundaries and states. Describe how to make links, input fields, and selected controls visually identifiable, including why placeholders or color alone may be inadequate cues.
- Visible keyboard focus. Explain what a focus indicator communicates to keyboard users and how its placement affects which adjacent colors it must contrast with.
- Contrast risks in shifting layouts. Explain how layout changes can move content onto low-contrast parts of gradient, image, or video backgrounds, and describe the need for predictable, contrast-safe layouts or background treatments.
- Responsive contrast testing. Describe how to verify contrast across viewport ranges, higher zoom levels, and supported orientations, including why manual checks should accompany automated ones.
- Color preferences and contrast. Explain why a site should respect users’ light or dark color preferences and maintain sufficient contrast in every supported scheme.
- CSS color scheme implementation. Trace how the example uses shared CSS theme variables, declares support for both schemes, and responds to a preferred dark scheme.
- Color as a supporting cue. Explain why information should remain understandable without color and how text, symbols, or patterns can provide another cue.
- Meaning and effort in images. Explain why image accessibility requires both giving users the same meaningful information and avoiding unnecessary effort to reach it.
- Purposeful image text alternatives. Describe how the section treats meaningful and decorative images differently when providing text alternatives.
- Decorative Images and Audio Clutter. Explain how to recognize a decorative image and why giving it an accessible name can make a page harder to use with a screen reader.
- Hiding Decorative Image Content. Describe the section’s ways to keep decorative images from being communicated to assistive technologies.
- Contextual alternative text. Explain how to write alternative text that communicates the information a simple image adds, rather than cataloguing its visual details. Give a concise description for an icon and include relevant contextual details for a photo.
- Human review of AI alt text. Justify treating AI-generated alternative text as a draft that an author must review and edit for the image’s purpose in context.
- Action-focused image alternatives. Explain why alternative text for a functional image describes what its link or button does rather than what the image depicts.
- Accessible names for icon controls. Describe how an icon-only interactive element gets an accessible name, and when visible text or an aria-label should supply that name.
- SVG embedding and accessibility. Distinguish the accessibility treatment of an SVG embedded with img from an inline svg, including what changes when either is decorative.
- Complex image text equivalents. Explain why a graph, diagram, or map needs both brief alt text and a full text equivalent of its information, rather than a long alt attribute.
- Description placement and association. Describe where to provide a complex image’s full text description and how to help readers find or associate it with the image.
- Accessible image map requirements. Explain what the image and each clickable area must convey through alt text, and how areas remain keyboard accessible.
- Accessible audio and video principles. Explain the two conditions this section gives for accessible audio and video: information or functionality must not depend on a single sensory channel, and users need some control over media behavior.
- Text alternatives for media information. Explain why information conveyed through audio, video, or animation also needs a programmatically accessible text alternative that carries the same information.
- Caption content and control. Explain what captions should convey and distinguish user-controlled closed captions from permanently embedded open captions.
- Transcript types and uses. Distinguish basic, descriptive, and interactive transcripts and explain why descriptive transcripts are recommended.
- Live media text alternatives. Explain the live-video and live-audio text alternatives described here, including approaches to real-time captioning and the need to correct recordings.
- Meaningful visual information in audio. Explain when a video needs audio description and distinguish standard from extended descriptions.
- Auto-playing audio disruption. Explain why audio that starts when a page loads can disrupt access, especially for someone using a screen reader, and why avoiding it is best practice.
- Playback controls and accessibility. State the rule for audio that auto-plays for more than three seconds and describe the playback controls the section calls for.
- Accessible alternatives to sound. Explain why a chime or other sound cannot be the only way an interface conveys an important message, and describe the visible and programmatic updates needed alongside it.
- Live region announcement roles. Describe how an ARIA live region communicates a dynamic update, and distinguish the timing and urgency of role="status" and role="alert".
What it builds on
- Meet your users (chapter 2) · Introduces the people who benefit from accessibility.
- Assistive technologies (chapter 2) · Introduces assistive technologies as ways people access content.
- When semantic HTML falls short: enter ARIA (and JS) (chapter 2) · The earlier introduction to ARIA provides context for the accessible-name example.
- The accessibility tree (chapter 2) · The accessibility tree and its role in what assistive technologies encounter.
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.
- Content perceivability across contexts: Explain why content must be perceivable across sensory channels, contexts of use, devices, browsers, and assistive technologies, rather than requiring people to use separate experiences.
Why it matters: This principle helps you ask whether people can actually receive and use the content you provide.
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.
- Sufficient contrast and legibility: Explain that sufficient contrast means text and UI elements stand out against their backgrounds so people can see, read, and use them. Describe why low contrast can make content difficult or impossible to read, especially under challenging viewing conditions or for people with vision impairments.
Why it matters: Content people cannot clearly see may be difficult or impossible for them to use.
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.
- WCAG contrast ratio model: Explain that WCAG calculates contrast from the relative luminance of foreground and background colors, producing a ratio from 1:1 to 21:1.
Why it matters: The ratio is the basis for checking WCAG contrast requirements. - Level AA contrast thresholds: State the main WCAG Level AA minimums: 4.5:1 for normal text and 3:1 for large text and meaningful non-text visuals, including UI components and focus indicators. Explain that larger text can remain visible at a lower ratio.
Why it matters: A measured ratio is useful only when compared with the requirement for that content. - APCA perceived contrast model: Describe how APCA reports perceived contrast as a Lightness Contrast (Lc) value rather than a WCAG ratio, accounting for text/background polarity and typography. Explain why a WCAG-passing combination can still be difficult to read.
Why it matters: Passing a minimum ratio does not always mean text is comfortably readable. - Conformance versus design guidance: Distinguish the roles of WCAG ratios and APCA: use the governing WCAG-based standard for conformance and APCA as supplementary guidance for design decisions.
Why it matters: Teams need to improve readability without mistaking design guidance for a compliance test. - Contrast tool limitations: Explain why automated contrast checks need manual follow-up across layouts and states: they inspect what is rendered at one point and can miss image text or changes at other viewports, zoom levels, and orientations.
Why it matters: A clean automated result can leave real contrast problems undiscovered. - Foreground background checking steps: Apply the section’s basic contrast-checking workflow: choose an element, obtain its foreground and directly underlying background colors, enter both into a checker, and compare the result with the relevant threshold.
Why it matters: The right measurement and threshold turn a visual concern into a checkable result.
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.
- Text contrast thresholds: Explain that WCAG minimum contrast ratios depend on text size and whether it is bold, and that the thresholds apply to text in interactive components and images as well as ordinary text.
Why it matters: Checking only ordinary page text can leave important interface text without sufficient contrast. - Readable disabled control text: Describe why text in disabled or inactive components should remain readable even though it need not meet the usual contrast thresholds.
Why it matters: An unreadable disabled control can confuse people rather than help them recognize that it is unavailable. - Contrast beyond minimum ratios: Explain why passing a minimum contrast ratio does not guarantee readable text and why maximum contrast is not always the aim.
Why it matters: A contrast check is a useful baseline, but readers still need text that is comfortable to read.
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.
- Non-text contrast baseline: Explain why contrast requirements apply to interactive components and meaningful graphics, not just text, and state the contrast values recommended in this section.
Why it matters: A control or graphic that blends into its surroundings may be difficult to use or missed entirely. - Control boundaries and states: Describe how to make links, input fields, and selected controls visually identifiable, including why placeholders or color alone may be inadequate cues.
Why it matters: Visible boundaries and states help people find controls and understand what they can do. - Visible keyboard focus: Explain what a focus indicator communicates to keyboard users and how its placement affects which adjacent colors it must contrast with.
Why it matters: Keyboard users need to see which control their next action will activate. - Meaningful graphic visibility: Describe the contrast and additional visual cues needed for informative icons and multiple data series in charts.
Why it matters: People can miss an icon’s meaning or misread a graph when its important parts blend together. - Non-text contrast exceptions: Distinguish cases exempt from the cited WCAG non-text contrast requirement from the continuing need for an understandable interface.
Why it matters: Knowing the exceptions helps you apply the requirement to meaningful information without treating every decorative border as essential. - Reduced-contrast form check: Trace the hands-on check that reveals faint form-field borders and the change that makes them visible.
Why it matters: The check makes an otherwise easy-to-miss contrast problem visible before users encounter it.
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.
- Contrast risks in shifting layouts: Explain how layout changes can move content onto low-contrast parts of gradient, image, or video backgrounds, and describe the need for predictable, contrast-safe layouts or background treatments.
Why it matters: A layout that looks readable on one screen can become hard to read on another. - Responsive contrast testing: Describe how to verify contrast across viewport ranges, higher zoom levels, and supported orientations, including why manual checks should accompany automated ones.
Why it matters: Checking multiple layouts helps catch contrast failures that a single-screen or automated test may miss.
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.
- Color preferences and contrast: Explain why a site should respect users’ light or dark color preferences and maintain sufficient contrast in every supported scheme.
Why it matters: A preferred theme is only useful if people can still perceive its content and controls. - CSS color scheme implementation: Trace how the example uses shared CSS theme variables, declares support for both schemes, and responds to a preferred dark scheme.
Why it matters: Shared theme variables make it possible to respond to a user’s scheme setting without changing colors separately throughout the stylesheet. - Maintainable theme design choices: Distinguish when paired light-dark() values or explicit theme rules are useful, and explain how system preferences and persistent manual overrides should interact.
Why it matters: Centralized, predictable theme choices make additional palettes easier to manage without disregarding users’ settings.
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.
- Color as a supporting cue: Explain why information should remain understandable without color and how text, symbols, or patterns can provide another cue.
Why it matters: People should still get the message when they cannot distinguish the colors you chose. - Alternatives in common UI: Apply the color-independent approach to forms, charts, status badges, and action labels using the alternatives given in this section.
Why it matters: The principle becomes useful when it changes how familiar controls and data displays communicate. - Meaningful symbol accessibility: Distinguish meaningful symbols from decorative ones and describe how to make meaningful symbols available to assistive technologies and understandable to users.
Why it matters: Replacing color with an icon only helps if people can perceive and interpret what the icon means. - Color perception checks: Describe how to check whether color-coded areas still communicate their meaning when colors are perceived differently or not seen at all.
Why it matters: Checking the interface under different color perceptions can reveal meaning that a design accidentally leaves in color alone.
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.
- Meaning and effort in images: Explain why image accessibility requires both giving users the same meaningful information and avoiding unnecessary effort to reach it.
Why it matters: An image can make a page less accessible either by obscuring important meaning or by interrupting the flow with needless content. - Purposeful image text alternatives: Describe how the section treats meaningful and decorative images differently when providing text alternatives.
Why it matters: Choosing text alternatives by an image’s purpose preserves useful information without adding needless announcements.
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.
- Decorative Images and Audio Clutter: Explain how to recognize a decorative image and why giving it an accessible name can make a page harder to use with a screen reader.
Why it matters: Keeping decoration out of announcements helps screen reader users find meaningful content without unnecessary interruptions. - Hiding Decorative Image Content: Describe the section’s ways to keep decorative images from being communicated to assistive technologies.
Why it matters: The right treatment lets people see the decoration without making assistive technology present it as content. - False Fixes and Verification: Explain why omitting alt or using presentation roles is not a reliable fix for decorative images, and how to check the result.
Why it matters: Checking the actual output catches decorative content that still reaches assistive technology despite a seemingly plausible fix.
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.
- Contextual alternative text: Explain how to write alternative text that communicates the information a simple image adds, rather than cataloguing its visual details. Give a concise description for an icon and include relevant contextual details for a photo.
Why it matters: Readers who cannot see the image need the information it contributes, not a list of visible objects. - Image information and redundancy: Distinguish a simple informative image that needs concise alternative text from an image whose information is already in the surrounding text or whose significant information needs a longer description.
Why it matters: Checking what an image adds avoids both repeating nearby text and omitting information. - Human review of AI alt text: Justify treating AI-generated alternative text as a draft that an author must review and edit for the image’s purpose in context.
Why it matters: A description can sound convincing while still withholding the information the image is meant to convey.
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.
- Action-focused image alternatives: Explain why alternative text for a functional image describes what its link or button does rather than what the image depicts.
Why it matters: People need to know what activating an image will do, not just what it looks like. - Accessible names for icon controls: Describe how an icon-only interactive element gets an accessible name, and when visible text or an aria-label should supply that name.
Why it matters: An icon-only button must communicate its purpose to someone who cannot see the icon. - Meaningful versus redundant icons: Distinguish an icon that adds information to a link from one that merely repeats information already in its text, and explain how each should be exposed.
Why it matters: This preserves useful warnings without making assistive technology repeat them. - SVG embedding and accessibility: Distinguish the accessibility treatment of an SVG embedded with img from an inline svg, including what changes when either is decorative.
Why it matters: The right way to expose an SVG depends on how it is embedded, not just on its file format.
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.
- Complex image text equivalents: Explain why a graph, diagram, or map needs both brief alt text and a full text equivalent of its information, rather than a long alt attribute.
Why it matters: A text equivalent lets people access the image’s underlying information without forcing them through an unwieldy image name. - Description placement and association: Describe where to provide a complex image’s full text description and how to help readers find or associate it with the image.
Why it matters: A findable text description makes the same information available to people who cannot or prefer not to use the image. - Detailed description attribute limitations: Explain why the section advises against relying on aria-describedby or longdesc for a complex image’s detailed description.
Why it matters: These limitations help explain why the section favors a description people can find and navigate in page content.
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.
- Image map structure: Describe how an image map creates multiple clickable regions in one image using a <map>, <area> elements, and an <img> with a usemap attribute.
Why it matters: This structure explains how one image can offer several distinct links. - Accessible image map requirements: Explain what the image and each clickable area must convey through alt text, and how areas remain keyboard accessible.
Why it matters: People need to understand both the image as a whole and its individual links, and be able to reach those links by keyboard.
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.
- Accessible audio and video principles: Explain the two conditions this section gives for accessible audio and video: information or functionality must not depend on a single sensory channel, and users need some control over media behavior.
Why it matters: These principles help keep media from becoming a barrier to using an application.
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.
- Text alternatives for media information: Explain why information conveyed through audio, video, or animation also needs a programmatically accessible text alternative that carries the same information.
Why it matters: A text alternative lets people get the information even when they cannot use the audio or visual channel.
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.
- Caption content and control: Explain what captions should convey and distinguish user-controlled closed captions from permanently embedded open captions.
Why it matters: Captions need to convey meaningful audio while giving viewers control when possible. - Timed caption tracks: Describe how a web video can provide closed captions using a separate timed text track and why generated captions need review.
Why it matters: A timed, accessible track lets viewers use captions without baking them into the video. - Transcript types and uses: Distinguish basic, descriptive, and interactive transcripts and explain why descriptive transcripts are recommended.
Why it matters: A transcript can preserve information for someone who cannot perceive the audio, the video, or both. - Live media text alternatives: Explain the live-video and live-audio text alternatives described here, including approaches to real-time captioning and the need to correct recordings.
Why it matters: Live accessibility depends on timely text, but publishing a recording also calls for an accurate lasting alternative. - Meaningful visual information in audio: Explain when a video needs audio description and distinguish standard from extended descriptions.
Why it matters: Someone listening without seeing the screen needs important visual events conveyed through sound. - Accessible playback and embeds: Describe the player controls, testing, and track information needed so people can use media alternatives, including third-party embeds.
Why it matters: Providing a caption track is not enough if viewers cannot find or operate its controls.
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.
- Auto-playing audio disruption: Explain why audio that starts when a page loads can disrupt access, especially for someone using a screen reader, and why avoiding it is best practice.
Why it matters: Avoiding unexpected audio lets people keep control of how they access a page. - Playback controls and accessibility: State the rule for audio that auto-plays for more than three seconds and describe the playback controls the section calls for.
Why it matters: Playback controls give users a way to manage media without silencing their entire device. - Browser auto-play limitations: Explain why browser blocking or muting of auto-playing media is not a sufficient accessibility safeguard.
Why it matters: An application still needs to handle audio accessibly even if one browser appears to suppress auto-play.
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.
- Accessible alternatives to sound: Explain why a chime or other sound cannot be the only way an interface conveys an important message, and describe the visible and programmatic updates needed alongside it.
Why it matters: People should not have to hear a sound to receive an important update. - Live region announcement roles: Describe how an ARIA live region communicates a dynamic update, and distinguish the timing and urgency of role="status" and role="alert".
Why it matters: Choosing the appropriate role helps users receive updates at a time that matches their urgency. - Restraint in audio announcements: Justify limiting live-region announcements and reserving role="alert" for critical, time-sensitive information.
Why it matters: Selective announcements preserve attention for updates that matter.
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
- (chapter intro) (chapter 4) · The preceding chapter’s focus on making content perceivable.
- Apply font readability guidelines (chapter 4) · Understanding that text needs sufficient contrast.
- Ensure keyboard focus is visible (chapter 5) · Contrast for UI components and graphics.
- Links done right (chapter 5) · contrast considerations when color distinguishes a link
- Revisiting the form (chapter 6) · Contrast in UI components
- Forms done right (chapter 6) · recognizing fields and their states in accessible forms
- Define language in single- and multilingual sites (chapter 4) · Meaning should not depend on a visual cue alone.
- Handle errors and help users recover effectively (chapter 6) · The need to convey meaning without relying on color alone
Concepts explained in this chapter
- contrast ratioA contrast ratio is a luminance-based numerical comparison between foreground and background colors, ranging from 1:1 to 21:1.
- lightness contrastAn APAC Lc value is a perceptual contrast metric expressing the lightness contrast between foreground and background colors.
- contrast requirementA contrast requirement is an accessibility requirement specifying that foreground content and its background must have enough visual difference for perception.
- sufficient contrastSufficient contrast is a visual design condition in which foreground text or interface elements are distinguishable from their background enough to support perception and reading.
- APCAAPCA is a perceptual color-contrast algorithm that estimates visual contrast using factors including lightness, polarity, font size, and font weight.
- relative luminanceRelative luminance is a normalized measure of the apparent brightness of a color based on the weighted contributions of its red, green, and blue channels.
- 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.
- decorative imageA decorative image adds no meaningful information beyond the surrounding content.
- audio descriptionAn audio description is spoken narration that conveys important visual information in audiovisual content.
- live regionA live region is a dynamically updated area of web content whose changes can be announced by assistive technologies.
- focus indicatorA focus indicator is a visible visual cue showing which interface element currently has keyboard focus.
- form fieldAn input field is an interface control that accepts user-entered data.
- graphical elementA graphical object is a visual element that conveys information or functionality through its shape, position, or appearance.
- captionA caption that viewers can turn on or off and that represents dialogue and relevant audio information.
- speech recognitionAutomated speech recognition is technology that converts spoken language into text without requiring a human transcriber to produce each word.
- WebVTTWebVTT is a web format for timed text tracks containing cues aligned with audio or video tracks.
- descriptive transcriptA descriptive transcript is a transcript that includes speech, non-speech audio, and necessary descriptions of visual details.
- live captioningLive captioning is the production and delivery of captions in real time during a live audiovisual event.
- media alternativeA media alternative is an alternate representation of audio or visual content that makes its information available through another format.
- media playerA media player is software that presents audiovisual content and provides controls for playback and related media features.
- track elementThe track element is an HTML element that associates timed text or other media tracks with audio or video.
- transcriptA written record of spoken content that can be read independently of its audio or video source.
- complex imageA complex image is a visual representation such as a chart, diagram, map, infographic, or flowchart whose meaning requires more than a short text alternative.
- aria-hiddenaria-hidden is an ARIA attribute that controls whether an element and its contents are exposed in the accessibility tree.
- informative imageAn informative image is a graphical image that conveys information or supplements information in surrounding content.
- functional imageA functional image is an image that triggers an action rather than conveying standalone information.
- readabilityReadability is the ease with which written content can be visually perceived and understood.
- accessible nameAn accessible name is the programmatically determined text label that identifies an interface element to users of assistive technologies.
- contrastColor contrast is the visual difference between foreground content and its background, typically resulting from differences in luminance or color.
- keyboard accessibilityThe ability to operate an interface through keyboard input without requiring a pointer or another input method.
- alert roleThe alert role is an ARIA live-region role for urgent, time-sensitive messages that require immediate attention.
- aria-livearia-live is an ARIA attribute that specifies how updates to a live region should be announced by assistive technologies.
- status roleThe ARIA status role identifies a live region for non-urgent updates that should not interrupt the current announcement.
- accessibility requirementAn accessibility requirement is a product or system requirement specifying accessibility obligations or capabilities that the system must satisfy.
- font-weightFont weight is a typographic setting controlling the thickness or boldness of text characters.
- hyperlinkA link is an interface element that points to another resource or location and enables navigation to it.
- interactive transcriptAn interactive transcript is a transcript whose text follows playback and allows users to navigate to corresponding media sections.
- open captionAn open caption is a caption permanently embedded in audiovisual content and displayed without user control.
- page titleThe title element is the HTML element whose text supplies a document's page title to user agents.
- cognitive loadCognitive load is the mental effort required to process information or complete a task.
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.
