liveBook · Manning

Accessibility

Digital accessibility is the extent to which digital content, products, and services can be perceived, understood, navigated, and used by people with diverse abilities and access needs.

How 9 Manning books explain it

D3.js in Action, Third Edition

Accessibility is the design of digital content and interfaces so that people with varying abilities can perceive, understand, navigate, and use them.

How it is used
Improves data visualizations so people with disabilities can reach their main conclusions and access underlying data.
How deep it goes
Works through a testable checklist and concrete chart changes, while leaving the full set of Chartability tests for further work.
Examples
Uses a cetacean scatterplot, readability checks, responsive axis labels, SVG descriptions, and a switchable data table.
What you can do after
Apply it via D3.js, semantic HTML, and SVG to improve a chart’s descriptions, data access, and interaction.

Read how D3.js in Action, Third Edition explains accessibility →

Architecting Accessibility

Digital accessibility is the design of digital products and services so that people with disabilities can perceive, operate, understand, and interact with them.

How it is used
Guides web product decisions toward removing barriers that prevent people with varied abilities, contexts, and technologies from completing tasks.
How deep it goes
Defines the practice, illustrates user barriers, and outlines team responsibilities and WCAG structure; stops short of a worked code implementation.
Examples
Uses color-only dashboard status, larger text, captions, keyboard access, and user personas to show how barriers affect tasks.
What you can do after
Practice/perform accessibility work throughout product development by considering varied user setups, choosing semantic code, and checking for barriers over time.

Read how Architecting Accessibility explains accessibility →

WordPress Power Toolkit: Harness AI to build next-level websites

Accessibility is the design and evaluation of digital content so that people with diverse abilities can perceive, understand, navigate, and interact with it.

How it is used
Makes website content and functionality usable for visitors with visual, hearing, motor, or cognitive challenges.
How deep it goes
Defines WCAG’s four principles and gives practical checks and fixes, but stops short of a complete compliance procedure.
Examples
Uses YouTube captions, image Alt Text, typography fixes, and accessibility-checker reports as concrete website tasks.
What you can do after
Apply it via WAVE or Lighthouse to identify issues, then manually improve typography, image descriptions, captions, and page structure.

Read how WordPress Power Toolkit: Harness AI to build next-level websites explains accessibility →

.NET MAUI in Action

Accessibility is the design of software interfaces so that people with disabilities can perceive, understand, navigate, and operate them.

How it is used
Adds semantic metadata to .NET MAUI UI so assistive technologies can communicate purpose, hierarchy, and input guidance.
How deep it goes
Introduces semantic descriptions, hints, heading levels, and limits of color cues; defers comprehensive accessibility study to external .NET MAUI resources.
Examples
Uses an image description, a Label heading level, and a location-sharing name Entry with a semantic hint.
What you can do after
Apply it via .NET MAUI semantic properties to describe interface elements for screen readers without relying solely on visual cues.

Read how .NET MAUI in Action explains accessibility →

React in Depth

The property of software being operable and understandable by people with diverse abilities and assistive technologies.

How it is used
Guides role-based React component tests and identifies accessibility work remaining in a reusable UI library.
How deep it goes
Explains implicit roles and accessible names through a component test, then inventories UI-library gaps without detailing WAI-ARIA internals.
Examples
Uses a MenuItem role-query test and a UI-library checklist covering translation, display preferences, motion, contrast, and font scaling.
What you can do after
Apply it via React Testing Library role queries, and evaluate reusable components against the identified accessibility gaps.

Read how React in Depth explains accessibility →

Tiny CSS Projects

Web accessibility is the design of web content and interfaces so that people with varied abilities and access methods can use them.

How it is used
Guides layout, loading feedback, animation, and text sizing so interfaces remain usable across different access methods and preferences.
How deep it goes
Provides practical checks and CSS choices for tab order, reduced motion, and scalable text; does not develop a comprehensive accessibility audit.
Examples
Uses a grid's tab-order display, an animated loader with a progress bar, and a profile card heading sized in rem.
What you can do after
Diagnose/debug with it by inspecting tab order in Firefox DevTools and emulating reduced motion in Chrome DevTools.

Read how Tiny CSS Projects explains accessibility →

Acing the Frontend Interview

Accessibility is the property of a user interface or document being usable by people with diverse abilities and assistive technologies.

How it is used
Assesses frontend implementation and interview reasoning about semantic structure, accessible interactions, forms, and production readiness.
How deep it goes
Connects semantic markup to accessibility, SEO, maintainability, and compatibility, then stops short of detailed assistive-technology testing.
Examples
Demonstrates accessibility through a React article page and discussions of semantic elements, forms, HTML APIs, and ARIA attributes.
What you can do after
Apply semantic HTML and appropriate ARIA while explaining accessibility trade-offs in React interviews and frontend implementation tasks.

Read how Acing the Frontend Interview explains accessibility →

Vanilla Web

The degree to which a product or service can be used by people with varied abilities and disabilities.

How it is used
Treats accessibility as a product requirement for interfaces usable across abilities, input methods, and contexts.
How deep it goes
Gives implementation rules for semantics, forms, contrast, and focus, but leaves detailed WCAG criteria to the guidelines.
Examples
Uses native buttons, a labeled email field with an associated hint, and custom-component focus questions as concrete cases.
What you can do after
Practice/perform accessible interface checks using native controls, labeled forms, keyboard testing, contrast checks, and assistive technology.

Read how Vanilla Web explains accessibility →

Everyday Data Visualization

Accessibility is the extent to which content or an interface can be perceived, operated, and understood by people with disabilities and varied access technologies.

How it is used
Frames accessibility as a practical design responsibility spanning perception, operation, understanding, and access technologies.
How deep it goes
Explains WCAG’s principles, guideline structure, conformance levels, color contrast, alternatives, and typography considerations.
Examples
Uses a blue-bar contrast comparison, a color-palette toggle, and an everyday example involving reading small text on a phone.
What you can do after
Apply WCAG 2.1 principles to evaluate color, typography, and accessible alternatives in interface designs.

Read how Everyday Data Visualization explains accessibility →

Also covered in

What to know first

Related concepts

Questions about accessibility

What is accessibility?

Digital accessibility is the extent to which digital content, products, and services can be perceived, understood, navigated, and used by people with diverse abilities and access needs.

Which Manning books explain accessibility?

D3.js in Action, Third Edition, Architecting Accessibility, WordPress Power Toolkit: Harness AI to build next-level websites, .NET MAUI in Action, React in Depth, Tiny CSS Projects, Acing the Frontend Interview, Vanilla Web and 1 more.

What should I know before learning accessibility?

Manning books that teach accessibility usually introduce visual impairment, disability, HTML and keyboard interaction first.

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.