Chapter 2: People, technologies, and fundamental techniques
The chapter introduction shifts attention from accessibility standards to the people, barriers, and technologies that should inform engineering decisions.
After this chapter you will be able to
- People-informed engineering decisions. Explain why understanding users’ real-world barriers and the strategies and technologies they use helps teams make accessibility decisions instead of relying on assumptions or quick fixes.
- Impairments and disabling barriers. Distinguish an impairment from a disability and explain why web accessibility focuses on removing barriers in the web rather than changing the person.
- Diverse and overlapping access needs. Describe the range of access needs represented by the users in this section, including temporary or situational limitations and co-occurring disabilities, and give a concrete example of a digital barrier.
- Everyday adaptive strategies. Explain that adaptive strategies are ways people configure or use mainstream tools and their accessibility features to make digital content easier to access, without requiring specialized hardware or software. Give examples and explain why people use them.
- Assistive technology and adaptive strategies. Distinguish assistive technologies from adaptive strategies while explaining their shared purpose.
- Limits of tools alone. Explain why assistive technology does not remove developers’ responsibility to make websites accessible.
- Overlay promise and limitations. Describe what accessibility overlays offer and explain why they cannot fix critical accessibility barriers in a site’s underlying code. Give examples of barriers the section identifies.
- Naturally accessible site code. Justify the section’s recommendation to build accessibility into site code, including its basic rule of using semantic HTML, rather than offloading responsibility to an overlay or model.
- Meaning Through Semantic HTML. Explain that semantic HTML uses elements according to their defined purposes to describe content’s meaning and structure independently of its appearance. Describe how that structure helps browsers communicate content to assistive technologies and helps search engines and AI systems interpret it.
- Built In Button Capabilities. Describe what using a native <button> provides without rebuilding those features: keyboard focus and activation, cancellable mouse and touch activation, information for assistive technology, and adaptation across platforms.
- Costs Of Div Impostors. Justify choosing appropriate native elements over repurposed <div> elements for controls or headings. Explain why retrofitting missing accessibility behavior creates maintenance work and may require replacing the components.
- Native elements over generic containers. Explain why the HTML element that describes content or an action should be preferred over a generic container or a custom replacement.
- Semantics in rendered components. Explain where to judge the accessibility semantics of a framework-built interface and what a well-designed component should render.
- Semantic page structure makeover. Describe how the example page replaces generic markup with elements for its major regions, headings, paragraphs, and lists, and explain the effect on screen reader navigation.
- Semantic HTML Before ARIA. Explain why native semantic elements are the first choice and when a custom component might warrant ARIA.
- ARIA Semantics Versus Behavior. Distinguish the accessibility information ARIA supplies from the behavior developers must implement, using the section's custom button example.
- Tab Roles And Relationships. Explain how the tab example communicates tab grouping, selection, and panel relationships to assistive technology.
- Tab Focus And Activation. Trace how keyboard focus, selection, and panel visibility work in the custom tabbed interface.
- Accessibility tree contents. Distinguish the accessibility tree from the DOM and describe the information it retains for assistive technologies.
- Dependence on semantic code. Explain why correct HTML semantics and ARIA information matter to the accessibility tree.
- Matching visible and accessible names. Explain why visible control labels should be included in accessible names and how the section’s examples illustrate this.
- Tree evaluation checks. Describe the principal structural and control-property checks recommended when evaluating an accessibility tree.
What it builds on
- What is web accessibility? (chapter 1) · Builds on the introduction to web accessibility.
- Where does accessibility fit in web projects? (chapter 1) · Assumes accessibility is considered across web-project work.
Section by section
Introduction
The chapter introduction shifts attention from accessibility standards to the people, barriers, and technologies that should inform engineering decisions.
- People-informed engineering decisions: Explain why understanding users’ real-world barriers and the strategies and technologies they use helps teams make accessibility decisions instead of relying on assumptions or quick fixes.
Why it matters: Accessibility decisions are better grounded in users’ actual experiences than in guesses or quick fixes.
Key terms: real-world barriers, strategies and technologies, informed engineering decisions
2.1 Meet your users
This section introduces the range of people and circumstances accessibility must account for, explains why barriers arise, and shows how personas can help teams design beyond assumptions about typical users.
- Impairments and disabling barriers: Distinguish an impairment from a disability and explain why web accessibility focuses on removing barriers in the web rather than changing the person.
Why it matters: This distinction directs attention toward changes a product team can make. - Diverse and overlapping access needs: Describe the range of access needs represented by the users in this section, including temporary or situational limitations and co-occurring disabilities, and give a concrete example of a digital barrier.
Why it matters: Recognizing varied circumstances helps teams notice barriers that an assumed typical user would miss. - Project-specific persona value: Explain why the chapter's personas are a starting point and how developing project-specific personas can help a team.
Why it matters: Personas can turn broad accessibility concerns into questions a product team can investigate. - Alternatives to conventional interaction: Explain why assuming browser use through a mouse and keyboard or touch is insufficient, and identify the broad alternatives people may use to access online content and functionality.
Why it matters: It keeps the team from treating conventional input as the only route to a product.
Key terms: impairment, disability, barriers, temporary or situational challenges, co-occurring disabilities, motor impairments, cognitive or learning disabilities, personas, project-specific personas, representative usability testing
2.2 Adaptive strategies
This section explains how people adapt everyday tools to access digital content and shows how website design can support or disrupt those strategies.
- Everyday adaptive strategies: Explain that adaptive strategies are ways people configure or use mainstream tools and their accessibility features to make digital content easier to access, without requiring specialized hardware or software. Give examples and explain why people use them.
Why it matters: Accessibility supports ways of using technology that many people rely on, sometimes only in particular circumstances. - Reading mode design compatibility: Explain how reading mode can reduce distractions and why some websites do not work well with it.
Why it matters: A design choice can determine whether someone’s preferred way of reading a page works. - Meeting assistant adaptation: Describe why Gill uses an AI meeting assistant during remote classes and what it provides beyond live captions.
Why it matters: One accessibility aid may not meet every need in a fast-moving conversation.
Key terms: adaptive strategies, accessibility features, keyboard-only interaction, closed captions, reading mode, semantic tags, proper headings, images of text, AI meeting assistant, live captions
2.3 Assistive technologies
This section explains what assistive technologies are, illustrates how people use them, and emphasizes that accessible websites remain developers’ responsibility.
- Assistive technology and adaptive strategies: Distinguish assistive technologies from adaptive strategies while explaining their shared purpose.
Why it matters: The distinction helps you recognize different ways people gain access without losing sight of their shared goal. - Assistive technology in everyday use: Describe how the section’s screen-reader and voice-control examples support access, including during a temporary injury.
Why it matters: These examples make clear that users may interact with a site in different ways, including while recovering from an injury. - Limits of tools alone: Explain why assistive technology does not remove developers’ responsibility to make websites accessible.
Why it matters: A person’s proficiency with an assistive tool cannot compensate for every barrier built into a website.
Key terms: assistive technologies, adaptive strategies, accessibility API, NVDA, screen reader, Voice Control, temporary limitations, learning curve, accessibility labels, inaccessible websites
2.4 The problem with accessibility overlays
This section explains why accessibility overlays cannot replace accessible site code and may conflict with users’ existing tools.
- Overlay promise and limitations: Describe what accessibility overlays offer and explain why they cannot fix critical accessibility barriers in a site’s underlying code. Give examples of barriers the section identifies.
Why it matters: A convenient control panel cannot make an essential task possible when the site itself prevents it. - Existing user accessibility setups: Explain why an overlay may be unnecessary or disruptive for someone who already uses browser or operating-system settings or assistive technology.
Why it matters: Accessibility features should work with a person’s existing setup rather than compete with it. - Context sensitive AI assistance: Explain why AI assistance with accessibility still needs human oversight, using the section’s example of informative-image text alternatives.
Why it matters: A plausible automated description is not necessarily the information a user needs in that context. - Naturally accessible site code: Justify the section’s recommendation to build accessibility into site code, including its basic rule of using semantic HTML, rather than offloading responsibility to an overlay or model.
Why it matters: Building accessibility into the site lets it work with the tools users choose for themselves.
Key terms: accessibility overlay, accessibility blockers, keyboard traps, missing labels, fake headings, browser or OS-level accessibility configurations, assistive technology, screen reader, AI, text alternatives
2.5 The fundamental rule: semantic HTML reigns supreme
This section explains why using HTML elements for their intended purposes makes web content understandable and interactive while avoiding unnecessary accessibility work.
- Meaning Through Semantic HTML: Explain that semantic HTML uses elements according to their defined purposes to describe content’s meaning and structure independently of its appearance. Describe how that structure helps browsers communicate content to assistive technologies and helps search engines and AI systems interpret it.
Why it matters: Meaningful markup helps people and software understand the same content without relying on how it looks. - Built In Button Capabilities: Describe what using a native <button> provides without rebuilding those features: keyboard focus and activation, cancellable mouse and touch activation, information for assistive technology, and adaptation across platforms.
Why it matters: Choosing a real button supplies useful interaction and accessibility behavior before any custom code is written. - Costs Of Div Impostors: Justify choosing appropriate native elements over repurposed <div> elements for controls or headings. Explain why retrofitting missing accessibility behavior creates maintenance work and may require replacing the components.
Why it matters: A quick-looking markup shortcut can turn into substantial accessibility and maintenance work.
Key terms: semantic HTML, meaning, structure, visual presentation, <button>, keyboard focus, button role, accessible name, pointer cancellation, <div>
2.5.1 Keep it POSH (Plain Old Semantic HTML)
This section shows how native semantic HTML makes a page easier to understand and navigate, then demonstrates how to improve and check a page’s markup.
- Native elements over generic containers: Explain why the HTML element that describes content or an action should be preferred over a generic container or a custom replacement.
Why it matters: Choosing a native element can spare you from rebuilding accessibility that the browser already provides. - Semantics in rendered components: Explain where to judge the accessibility semantics of a framework-built interface and what a well-designed component should render.
Why it matters: A component’s name cannot compensate for inaccessible HTML output. - Semantic page structure makeover: Describe how the example page replaces generic markup with elements for its major regions, headings, paragraphs, and lists, and explain the effect on screen reader navigation.
Why it matters: Meaningful structure turns a page into regions and content that readers can identify and skip between. - Distinguishable navigation and page context: Describe the additional markup used to distinguish multiple navigation areas, identify the current page, and specify the page language.
Why it matters: These small additions help users tell navigation areas apart, locate themselves, and hear the page in the right language. - Checking structure without visual styling: Explain how removing custom CSS and exploring headings and landmarks with a screen reader can reveal whether a page’s structure stands on its own.
Why it matters: Checking the underlying structure catches problems that a polished visual design can hide. - Boundaries of semantic HTML review: Describe what the supplied semantic-HTML review prompt can assess and why findings from source HTML alone must be qualified.
Why it matters: A useful markup review reports what its evidence supports without presenting a partial check as a full audit.
Key terms: native HTML, semantic HTML, <div>, <span>, POSH, rendered interface, components, native semantics, Shadow DOM, <header>
2.5.2 When semantic HTML falls short: enter ARIA (and JS)
This section explains when custom interfaces need ARIA, why ARIA must be paired with working behavior, and how an accessible tabbed interface puts those principles into practice.
- Semantic HTML Before ARIA: Explain why native semantic elements are the first choice and when a custom component might warrant ARIA.
Why it matters: Choosing native elements where possible avoids rebuilding accessibility features yourself. - ARIA Semantics Versus Behavior: Distinguish the accessibility information ARIA supplies from the behavior developers must implement, using the section's custom button example.
Why it matters: A component can be announced correctly by a screen reader yet still be impossible to use. - Custom Component Guidance And Testing: Describe how the Authoring Practices Guide and hands-on testing help assess custom components, including third-party ones.
Why it matters: A documented pattern or the presence of ARIA attributes is not proof that the finished component is usable. - Tab Roles And Relationships: Explain how the tab example communicates tab grouping, selection, and panel relationships to assistive technology.
Why it matters: These relationships let assistive technology users identify the tabs, their current selection, and the content they control. - Tab Focus And Activation: Trace how keyboard focus, selection, and panel visibility work in the custom tabbed interface.
Why it matters: Without coordinated keyboard behavior and state changes, tabs may look right but remain difficult or impossible to navigate.
Key terms: semantic HTML, native elements, ARIA, custom components, ARIA roles, states, properties, role="button", tabindex, JavaScript
2.5.3 The accessibility tree
This section explains how browsers turn semantic HTML into accessibility information for assistive technologies and shows how to inspect that information for problems.
- Accessibility tree contents: Distinguish the accessibility tree from the DOM and describe the information it retains for assistive technologies.
Why it matters: The tree helps explain what assistive technologies can perceive about a page. - Dependence on semantic code: Explain why correct HTML semantics and ARIA information matter to the accessibility tree.
Why it matters: Incorrect semantics can cause assistive technology to announce the wrong thing. - Accessibility API bridge: Trace how accessibility-tree information and page changes reach assistive technologies.
Why it matters: This bridge explains how assistive technologies obtain page information and notice changes. - Matching visible and accessible names: Explain why visible control labels should be included in accessible names and how the section’s examples illustrate this.
Why it matters: A name mismatch can make a visible control frustrating or unreliable to use by voice. - Accessibility tree inspection: Describe how to open a browser’s accessibility view and inspect an element’s properties.
Why it matters: Inspecting what the browser exposes can reveal problems that are not obvious visually. - Tree evaluation checks: Describe the principal structural and control-property checks recommended when evaluating an accessibility tree.
Why it matters: These checks turn an accessibility-tree inspection into a practical review of page structure and controls.
Key terms: accessibility tree, DOM tree, role, state, accessible name, semantically correct, HTML, ARIA, Accessibility API, accessibility layer
2.6 Summary
2.7 References
This section lists sources cited in chapter 2 without explaining new accessibility concepts or techniques.
Where this is used later
- (chapter intro) (chapter 3) · Introduces the people who benefit from accessibility.
- Design for imprecision: touch, gaze, and mouse pointing (chapter 5) · Provides context for designing interactions that do not assume precise pointing.
- Build keyboard-friendly websites (chapter 5) · Keyboard-friendly development addresses barriers such as keyboard traps.
- Offer appropriate labels (chapter 6) · Form labels must be provided rather than left for an overlay to guess.
- Simple informative images (chapter 3) · Informative-image alternatives require attention to the image’s purpose.
- Define language in single- and multilingual sites (chapter 4) · HTML elements and attributes convey meaning to assistive technologies.
- Rely on native HTML (chapter 6) · Supports the choice to rely on native HTML in forms.
- Avoid impostor ARIA components – unless you must! (chapter 6) · Provides the rationale for caution about impostor components.
Concepts explained in this chapter
- semantic markupSemantic HTML is the use of HTML elements whose names and structure convey the meaning, role, and organization of content.
- custom controlA custom component is a developer-created interface component whose roles, states, labels, and behavior must be exposed to assistive technologies.
- landmarkA semantic region identifying a major area of a page, such as navigation or main content, for assistive-technology navigation.
- ARIA labelaria-label is an ARIA attribute that assigns an accessible name to an interface element.
- aria-currentaria-current is an ARIA attribute that identifies the item representing the current location or state within a related set.
- lang attributeThe lang attribute identifies the natural language of an HTML element's content.
- assistive technologyAssistive technology is hardware or software that enables people with disabilities to access, perceive, control, or interact with digital content and systems.
- WAI-ARIAARIA is a W3C standard for adding accessibility semantics and interaction-state information to web content and user interface widgets.
- accessibility treeAn accessibility tree is a browser-maintained representation of interface elements and their accessibility roles, states, properties, and relationships exposed to assistive technologies.
- ARIA roleAn ARIA role is a semantic classification assigned to an interface element to communicate its widget or structural type to assistive technologies.
- WAI-ARIA Authoring Practices GuideThe ARIA Authoring Practices Guide is an informative, example-driven W3C resource describing ARIA semantics, interaction patterns, and expected keyboard behavior for interface components.
- focus managementFocus management is the deliberate control of keyboard focus movement, placement, and return within an interactive interface.
- roving tabindexRoving tabindex is a keyboard-focus pattern in which only one element in a composite widget is included in the sequential focus order at a time.
- tab panelA tab panel is the content region associated with and displayed by a tab in a tabbed interface.
- tabbed interfaceA tabbed interface is a composite user-interface pattern in which tabs control the visibility of corresponding content panels.
- tabindexAn HTML global attribute that controls an element’s keyboard focusability and position in sequential focus navigation.
- accessibility overlayAn accessibility overlay is a software layer added to a digital interface to modify presentation or interaction features intended to improve accessibility.
- accessibility APIAn accessibility API is a platform interface through which applications expose user-interface structure, meaning, state, and functionality to assistive technologies.
- accessible nameAn accessible name is the programmatically determined text label that identifies an interface element to users of assistive technologies.
- adaptive strategyAn adaptive strategy is a user-specific method of configuring or using mainstream devices, software, or built-in accessibility features to accommodate individual needs.
- accessibility barrierAn accessibility barrier is a feature, condition, or design decision that prevents or impedes people from accessing or using technology.
- 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.
- accessibilityDigital accessibility is the design of digital products and services so that people with disabilities can perceive, operate, understand, and interact with them.
- disabilityA disability is a physical, sensory, cognitive, or other condition that can affect a person's ability to interact with technology.
- functional limitationA functional limitation is a restriction in performing an activity that results from a person's abilities or impairments.
- impairmentAn impairment is a difference or reduction in a person's physical, sensory, cognitive, or other functioning that may create functional limitations.
- personaA persona is a representative user model that describes relevant characteristics, needs, constraints, and goals for reasoning about product use.
- voice controlVoice control is an input technology that lets users operate software or hardware through spoken commands.
- image of textText rendered as pixels within an image rather than exposed as separately usable digital text.
- buttonA button element is an HTML control for triggering an action through built-in keyboard, pointer, focus, and accessibility behavior.
- keyboard interactionOperating an interface using only a keyboard, without relying on a pointing device.
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.
