Accessibility
Accessibility is the degree to which a product, service, system, or information can be accessed, understood, and used by people with diverse abilities and access needs.
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
- Guides construction of data visualizations that convey conclusions and interactions to users with disabilities.
- How deep it goes
- Works through a checklist and concrete HTML, SVG, D3, table, and responsive-style changes without exhaustively covering WCAG.
- Examples
- Uses a cetacean scatterplot, filter buttons, SVG descriptions, responsive axis labels, and a switchable downloadable data table.
- What you can do after
- Apply it via D3 and HTML to improve chart text, semantics, screen-reader context, keyboard access, alternatives, and responsive behavior.
Read how D3.js in Action, Third Edition 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
- Guides website design, media embedding, and review toward use by people with diverse impairments.
- How deep it goes
- Explains POUR principles and practical checks, while deferring complete automated compliance to manual review.
- Examples
- Demonstrates caption-enabled YouTube embedding and evaluates pages with WAVE, Monsido, Siteimprove, and Lighthouse.
- What you can do after
- Operate/configure it by adding Alt Text and captions, improving structure and typography, then acting on accessibility audit findings.
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.
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.
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.
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 →
Related concepts
- semantic propertiesused by · Semantic properties are .NET MAUI UI metadata that communicates accessibility meaning, such as heading level, to assistive technologies.
- WCAGmeasured by · WCAG is a W3C standard providing testable recommendations and success criteria for making web content accessible to people with disabilities.
- WAI-ARIAcontrasts with · WAI-ARIA is a W3C specification defining roles, states, properties, and other accessibility semantics for communicating web interface information to assistive technologies.
- assistive technologyuses · Assistive technology is hardware or software that enables people with disabilities to access, perceive, control, or interact with digital content and systems.
- Lighthousemeasured by · Lighthouse is an open-source tool that audits web pages for performance, accessibility, best practices, search engine optimization, and progressive web app characteristics.
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.