Accessibility

The design commitment to keep a system perceivable, operable, understandable, and robust for the full distribution of intended users including the sensory, motor, cognitive, and infrastructural tails — by designing to those tails rather than to the median.

Core Idea

Accessibility is the design commitment that a system's interface, content, and processes stay perceivable, operable, understandable, and robust for the full distribution of intended users, including the tails of sensory, motor, cognitive, linguistic, and infrastructural variation. Its mechanism is designing to the tails rather than the median: every design silently encodes an assumed-capability profile, and wherever the actual population exceeds that profile users are excluded — a defect to measure and adjust, operationalized in HCI through WCAG.

Scope of Application

Accessibility lives across the design fields — human-computer interaction, the built environment, and universal design — unified by one commitment to design for the full user distribution rather than the median, within those design disciplines.

• Human-computer interaction and web standards — the densest habitat; WCAG criteria, ARIA, contrast, captions.
• Architecture and the built environment — the origin domain; ramps, tactile paving, high-contrast signage.
• Communication and education — plain-language drafting and multimodal lessons for the linguistic tails.
• Public-service and policy design — low-literacy forms, multilingual, bandwidth-tolerant services.
• Industrial and product design — levers over doorknobs, tactile labels, captioned safety briefings.

Clarity

Naming accessibility makes visible the assumed-capability profile every design silently encodes and normally mistakes for a natural baseline. It turns that profile into an explicit, measurable parameter and reframes the resulting gap from a defensible scoping decision into a defect, converting "is this inclusive?" into the sharp question "which tails does this exclude, along which dimension, and is that intended?" It also sharpens designed-in inclusion versus bolt-on accommodation, and charity versus structural investment.

Manages Complexity

The space of users a design must serve is unbounded — every combination of capabilities is a distinct population. Accessibility compresses that enumeration into one object: the assumed-capability profile, a small set of parameters with testable thresholds. The designer tracks that handful and reads exclusion off the comparison against the actual distribution. The designed-in-versus-bolt-on fork predicts which accommodations will decay, and the curb-cut branch predicts which will pay broad dividends, from the same parameters.

Abstract Reasoning

Accessibility licenses diagnostic reasoning — surfacing the assumed-capability profile and the tails it excludes, checkable against WCAG. It supports predictive reasoning that forecasts bolt-on decay from the accommodation architecture and anticipates curb-cut spillover as a feature-selection rule, and interventionist reasoning that adjusts the shared profile rather than bolting on per-population fixes and designs in early to drop cost.

Knowledge Transfer

Within HCI, the built environment, and universal design accessibility transfers intact as mechanism — only the dimensions and thresholds change. Beyond those fields the transfer is largely of commitment (plan for the tails) rather than mechanism. Its structural content reinstantiates more general patterns: design-to-the-tails as distribution-as-spec, the curb-cut effect as positive externalities of inclusion, bolt-on decay as divergent maintenance of parallel pathways, and the early-design cost advantage. Those general primes carry the cross-domain lesson; the name stays home.

Relationships to Other Abstractions

Current abstraction Accessibility Domain-specific

Parents (4) — more general patterns this builds on

• Accessibility is part of Keyboard Accessibility Domain-specific

  Accessibility contains Keyboard Accessibility as its channel-completeness obligation for interactive functions operated without a pointer.

• Accessibility is part of Perceivable Design Domain-specific

  Accessibility contains Perceivable Design as the obligation that essential signals remain available when a user cannot access the default sensory channel.

• Accessibility is part of Robust Accessibility Domain-specific

  Accessibility contains Robust Accessibility as the obligation that assistive technologies can recover meaning from explicit structural semantics.

• Accessibility is part of Affordance Prime

  Accessibility contains affordance because operability for a capability distribution is the set of actions made possible by each user's fit with the designed environment.

Children (1) — more specific cases that build on this

• Complete Streets Domain-specific is a kind of Accessibility

  Complete Streets is accessibility specialized to a public road corridor whose intended-user distribution includes every mobility mode, age, and ability class.

Hierarchy paths (28) — routes to 11 parentless roots

• Accessibility → Keyboard Accessibility → Functional Redundancy (Degeneracy) → Redundancy → Reserve → Economy Of Force → Allocation → Scarcity → Constraint

Show alternative paths (27)

Neighborhood in Abstraction Space

Accessibility sits in a crowded region of the domain-specific corpus (37^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Surface Form & Underlying Structure (23 abstractions)

Nearest neighbors

• Discoverability — 0.86
• Robust Accessibility — 0.85
• Touch-Target Miss — 0.85
• Discoverability Failure — 0.84
• Screen-Reader Ambiguity — 0.84

Computed from structural-signature embeddings · 2026-07-12