Human Capacity Accommodation Design

Diagnose the mismatch between human capacity and system demand, then change the task, environment, interface, timing, modality, or support so people can achieve essential outcomes safely and with dignity.

Essence

Diagnose mismatch between human capacity and system demand, then change the task, environment, interface, timing, modality, or support so people can achieve essential outcomes safely and with dignity. Preserve the outcome, not an inherited method that excludes users.

The unit of analysis is fit, not the isolated person. A capacity can be sufficient in one setting and overwhelmed in another because the required rate, duration, precision, sensory channel, interruption tolerance, recovery time, or social exposure changed. Conversely, a demanding task can become workable when its sequencing, interface, tool, environment, timing, or assistance changes. This relational view prevents the design team from treating every difficulty as a deficit located inside the user.

Accommodation is therefore a governed transformation of demand. It may remove a nonessential requirement, distribute effort across time, substitute an equivalent modality, introduce an assistive bridge, change the physical environment, supply human support, or create a protected recovery path. The transformation is successful only when the person can reach the meaningful outcome with comparable agency, timeliness, safety, privacy, and remedy—and when the path remains operable after the pilot ends.

Compression statement

Systems often encode an imagined standard user and treat deviations in sensory, motor, cognitive, linguistic, emotional, health, age, fatigue, stress, or situational capacity as personal failure. Human-Capacity Accommodation Design defines essential outcomes separately from inherited methods; maps representative capability ranges and fluctuation; analyzes person-task-environment mismatch; identifies preventable demand and barriers; co-designs equivalent alternatives, adjustments, assistive interfaces, pacing, recovery, and support; checks safety, privacy, stigma, workload transfer, and feasibility; implements with consent and accountable ownership; validates in real contexts; monitors breakdown, drift, maintenance, and inequity; and revises without forcing repeated disclosure.

Canonical formula: essential_outcome_and_context + representative_capacity_envelope + demand_and_barrier_map + mismatch_and_risk_analysis + co_designed_accommodation_options + equivalence_safety_dignity_gate + implementation_and_support + in_use_validation_and_revision -> durable_human_system_fit

When to Use This Archetype

Use it when sensory, motor, cognitive, linguistic, emotional, health, fatigue, or situational limits interact with task or environmental demands; when workarounds and support are hidden; or when alternate methods can preserve the same meaningful outcome.

Use User Context Validation when only assumptions need testing, Cognitive Load Reduction for information burden alone, and ordinary simplification when a barrier can be removed for everyone without accommodation governance.

Strong application signals

The pattern is especially useful when performance varies sharply across apparently similar people or across the same person's day; when successful completion depends on undocumented assistance; when people avoid a channel before entering the measured funnel; when a nominally optional method is practically mandatory; or when an accessibility exception exists but requires delay, repeated proof, public disclosure, or exceptional persistence. These signals point to a capacity-demand relation rather than a simple knowledge gap.

Use the full lifecycle when the accommodation has dependencies that can decay: configured technology, trained staff, an interpreter roster, a modified schedule, a physical device, a synchronized alternate workflow, or a manager decision. A one-time adjustment may be enough for a temporary low-risk task, but a recurring or safety-relevant accommodation needs ownership, fallback, maintenance, and revision.

The archetype also applies before an individual requests help. Population-level evidence can reveal predictable exclusion and support inclusive defaults. Individual choice remains necessary because people with similar diagnoses or labels can have different capacities, strategies, preferences, risks, and privacy boundaries.

Structural Problem

Systems encode an imagined standard user and misclassify predictable mismatch as low motivation or inability. Fixed modality, pace, posture, language, location, or disclosure requirements exclude capable people, create error and injury, and transfer effort to users and support networks.

Diagnose demand before prescribing support

A mature diagnosis separates at least five layers. The essential outcome is the result that must be achieved. The task method is the current sequence used to reach it. The demand profile describes what that sequence asks of perception, movement, memory, attention, language, endurance, emotional regulation, and time. The capacity envelope describes what a person or population can reliably supply under relevant conditions. The consequence map records what happens when demand exceeds capacity: error, pain, abandonment, unsafe work, delayed service, stigma, disclosure, or transferred labor.

Demand is multidimensional and cumulative. A form may be readable but still inaccessible because it times out; a workstation may be reachable but not sustainable for a full shift; a meeting may provide captions but combine rapid turn-taking, ambiguous agendas, sensory load, and no recovery interval. Profile peak demand, sustained demand, switching cost, simultaneous demand, and recovery debt—not merely whether each isolated action is possible once.

Capacity is likewise a range rather than a fixed score. It changes with fatigue, medication, pain, stress, environmental noise, acute illness, sleep, competing caregiving, unfamiliarity, and prior effort. Design against the reliable operating envelope and relevant worst-reasonable conditions, while keeping enough adjustability for individual strategy. Designing to a population average systematically hides tails, intersections, and fluctuation.

Evidence must include absent and unsuccessful users. Completion data describe survivors. Workarounds, abandoned attempts, requests routed elsewhere, family assistance, staff rescue, injury reports, and nonparticipation often reveal the actual mismatch. The diagnostic question is not only “Can a person complete this?” but “At what effort, risk, delay, dependency, and probability of recovery?”

Intervention Logic

Separate essential outcomes and safety constraints from inherited methods. Map representative capacity ranges and fluctuation, decompose task and environmental demands, and link mismatch to barriers and harm. Co-design inclusive defaults and equivalent paths; test outcome, safety, dignity, privacy, effort, delay, assistive compatibility, and burden transfer. Implement with ownership, maintenance, backup, and repair, then validate in real contexts and revise.

1. Frame the outcome and authority

Write the essential outcome in method-neutral terms and identify who has authority to challenge each requirement. Trace safety claims to evidence, not tradition. A requirement such as “respond within five seconds,” “appear in person,” “lift this object manually,” or “speak without assistance” may be essential, partially essential, or merely inherited. Record the reason, consequence of relaxation, and available compensating controls.

2. Build capacity and demand profiles

Profile relevant capacity dimensions only; do not collect diagnostic detail because it is available. For each task segment, record modality, force or dexterity, precision, reach, posture, memory load, attention duration, switching frequency, language complexity, emotional exposure, social coordination, pace, duration, recovery opportunity, and environmental conditions. Mark which demands are adjustable, substitutable, sequence-dependent, or coupled to other demands.

3. Locate and prioritize mismatches

Cross the profiles and rank mismatches by severity, frequency, irreversibility, inequity, and effect on the essential outcome. Distinguish a barrier from a coping strategy: a colleague completing the inaccessible step is evidence of mismatch, not proof that the process works. Prioritize bottlenecks that block entry, create injury, force disclosure, or make later recovery impossible.

4. Transform demand and generate options

Start with removal of nonessential demand, then consider redistribution, substitution, augmentation, assistance, and recovery. Combine inclusive defaults with personal configuration. A strong option set includes more than one feasible path when needs can conflict: quiet space may help one person while remote participation helps another; slower pacing may improve accuracy while creating fatigue for someone else. Co-design exposes these interactions before a single “accessible solution” becomes another fixed standard.

5. Gate for meaningful equivalence

Compare options using the same outcome and consequence measures as the primary path. Test safety, completion, quality, time, effort, privacy, independence, social exposure, access to appeal, and reliability. The alternative need not be identical, but it must not impose a material penalty unrelated to the essential outcome. When perfect equivalence is impossible, make the residual difference explicit, obtain informed choice where appropriate, and assign authority to mitigate or review it.

6. Operationalize, rehearse, and revise

Treat configuration, procurement, training, scheduling, staffing, funding, documentation, handoff, maintenance, security, backup, repair, and change synchronization as part of the design. Rehearse failures before dependence becomes critical. Validate in actual contexts and under capacity variation, then feed outcome, effort, incidents, abandonment, support burden, and repair time into a revision loop. The lifecycle closes only when detected mismatch can trigger a funded change.

Key Components

The outcome and context frame defines what matters. The capacity profile represents human variation. The demand map locates system requirements. The mismatch ledger links them to consequences. The option set generates alternatives. The safety and dignity gate tests equivalence. The implementation plan sustains delivery. The fit monitor detects breakdown and change.

Component	Description
Essential outcome, user, and context frame ↗	This frame prevents method lock-in. It identifies the person or population, the setting, the meaningful result, true safety constraints, affected third parties, decision authority, and the methods currently treated as mandatory. It should explicitly name excluded nonusers and downstream recipients of transferred work. Without this frame, teams optimize the existing procedure and call the optimization accommodation.
Representative capacity and variability profile ↗	The profile describes functional ranges in context rather than inferring needs from identity labels. It includes fluctuation, compensating strategies, cumulative fatigue, recovery, and intersections among capacities. Its detail should be proportional to the decision: enough to choose and test an accommodation, no more than necessary for privacy and governance.
Task, environment, and interface demand map ↗	The demand map decomposes the system side of the relation. It records peak and sustained loads, simultaneity, transitions, interruption, precision, timing, environment, and social requirements. It also shows where one demand amplifies another—for example, time pressure can increase memory load and error cost, while noise can increase listening effort and fatigue.
Mismatch, barrier, workaround, and risk ledger ↗	The ledger joins evidence to consequence. Each entry states the demand, affected capacity range, context, observed or credible consequence, existing workaround, burden bearer, uncertainty, and priority. Keeping assumptions separate from observations lets users contest deficit-based interpretations and helps reviewers see where more evidence is needed.
Accommodation option and equivalent-path set ↗	The option set spans universal changes, configurable defaults, individual adjustments, assistive technologies, environmental changes, human support, and fallback. Options are composable: adjustable timing alone may not help if error recovery remains inaccessible. The set preserves choice and records why rejected options failed equivalence, safety, feasibility, or user-preference tests.
Safety, dignity, privacy, and burden gate ↗	This gate stops cheap but inferior alternatives from passing as accommodations. It evaluates risk controls, agency, disclosure, stigma, time, effort, quality, independence, remedy, and burden transfer. Decisions are documented and contestable, especially when cost or operational convenience is weighed against exclusion.
Implementation, support, and ownership plan ↗	Approval without delivery is not accommodation. The plan names owners, dates, funding, dependencies, configuration, training, support hours, handoffs, spares, repair targets, and synchronization with the primary system. It keeps the user from becoming the unpaid program manager for their own access.
In-context fit, breakdown, and revision monitor ↗	The monitor observes whether the path works over time without turning into surveillance. It tracks meaningful outcomes, effort, errors, abandonment, failure, repair, disparity, and support load at the minimum granularity needed. Findings connect to a revision owner and response threshold; otherwise monitoring merely documents harm.

Common Mechanisms

Person–task–environment analysis locates mismatch. Essential-function review challenges inherited methods. Participatory workshops generate options. Multimodal and assistive tests establish equivalence. Failure rehearsals test backup and repair. Longitudinal audits reveal disparity, decay, and shifted burden.

These mechanisms implement different stages and should not be mistaken for the parent pattern. A mismatch analysis can produce a correct diagnosis but no funded change. A workshop can generate attractive options without safety evidence. An automated accessibility scan can find some technical defects while missing timing, cognitive effort, social exposure, and recovery. The archetype coordinates their outputs into a durable accommodation lifecycle.

Select mechanisms according to uncertainty and consequence. Use direct contextual observation where workarounds hide demand; structured task analysis where sequencing and concurrency matter; participatory option generation where preferences and conflicting needs are central; instrumented testing where timing, force, error, or compatibility requires measurement; and longitudinal audit where adaptation, drift, or burden transfer may appear slowly. High-risk changes need independent safety review and rehearsed fallback in addition to user validation.

Mechanisms should accept qualitative evidence. A person's report of pain, overload, stigma, or unsustainable effort is not invalid because the system lacks a sensor for it. Triangulate self-report, observation, outcome data, incidents, and support-worker knowledge while avoiding demands for repeated proof. Evidence thresholds should rise with the risk of the proposed change, not with skepticism toward the claimant.

• Accommodation Failure and Recovery Rehearsal
• Essential-Function and Method-Separation Review
• Longitudinal Fit, Equity, and Burden Audit
• Multimodal Equivalence and Assistive-Compatibility Test
• Participatory Accommodation-Option Workshop
• Person–Task–Environment Mismatch Analysis

Parameter / Tuning Dimensions

Tune user and context segmentation, capability dimensions, evidence granularity, essential-function threshold, customization range, safety margin, disclosure minimum, equivalent-outcome standard, support level, repair time, backup capacity, and review cadence.

Workload, rate, and complexity

Tune intensity, duration, repetition, concurrency, precision, and recovery separately. Lowering the average workload may leave a peak bottleneck untouched. Slowing a task can reduce time pressure but increase exposure and fatigue; splitting a task can lower memory load but add transitions. Complexity can be reduced, scaffolded, externalized, or distributed without removing the meaningful challenge or decision.

Modality and interaction freedom

Tune which sensory and motor channels are required, whether modalities can be combined, and whether users can switch without losing state. Avoid making the alternative path a dead end: equivalent error messages, authentication, help, confirmation, appeal, and recovery matter as much as the happy path. Assistive compatibility should be tested as an interaction among tool, content, device, policy, and support—not assumed from nominal standards conformance.

Personalization breadth and control

Set the range of adjustable values, who may change them, whether changes persist, and how defaults are chosen. Too little range creates false flexibility; too much unbounded variation can create safety, support, and maintenance problems. Favor user-controlled reversible settings inside a validated envelope, with accountable exception handling beyond it.

Evidence, privacy, and review cadence

Tune evidence to the least intrusive information needed for the decision. Prefer functional need and desired outcome over diagnosis. Set expiration and revalidation only when the underlying context is likely to change and the benefit justifies the burden. Review cadence should follow risk, system change, failure history, and capacity fluctuation—not an arbitrary annual demand for recertification.

Service and recovery levels

Define provisioning lead time, support availability, maximum outage, fallback capacity, escalation time, repair time, and communication during failure. A low-frequency accommodation can still be mission-critical. Service targets should reflect consequence of loss rather than average usage volume.

Invariants to Preserve

• Essential outcome, inherited method, and safety constraint remain distinct.
• Capacity evidence represents range and fluctuation, including excluded nonusers.
• Affected people have choice and can contest mismatch assumptions.
• Accommodation does not silently shift unreasonable burden.
• Privacy, dignity, autonomy, and nonretaliation are preserved.
• Alternate modes receive equivalent testing, maintenance, and change control.
• Real-context validation and rapid repair remain available.

Preserving dignity does not mean avoiding measurement; it means measuring the system without making the person prove worthiness. Participation must be voluntary and informed, with safe ways to disagree, decline a proposed aid, or request another path. Data about functional need should be separated from general performance management and access-controlled according to purpose.

Preserving equity means evaluating both access to accommodation and quality after accommodation. A technically available path that takes longer, costs more, provides less privacy, limits advancement, or depends on discretionary goodwill is structurally unequal. Compare who knows the path exists, who can request it, who waits, who is denied, who carries coordination work, and who receives timely repair.

Safety is an invariant and a subject of redesign, not a blanket veto. When an inherited method is defended as safe, identify the hazard and required control. Alternative controls may provide equivalent or better risk reduction. When equivalence cannot be established, record the residual risk, decision authority, affected person's role, and review trigger.

Target Outcomes

Expect greater safe access and completion, lower avoidable effort and error, less stigma and forced disclosure, more resilient performance, reduced workaround debt, and better-maintained inclusive systems.

Track outcome quality and sustainability, not request volume alone. Useful measures include completion among previously excluded users, error and injury rates, avoidable effort, time and delay, abandonment, support dependency, disclosure events, repair time, recurrence, parity after system changes, and distribution across groups and modalities. Pair quantitative signals with accounts of agency, dignity, predictability, and perceived safety.

A strong intervention can benefit people beyond the initially named group: adjustable timing supports fatigue and interruptions; clear state and recovery support novice and expert users; reduced force and neutral posture reduce cumulative injury; multiple communication modes improve resilience during channel failure. These spillovers are evidence of robust design, but they should not erase the need for individual accommodation where universal defaults cannot resolve conflicting or uncommon needs.

Tradeoffs

Common defaults conflict with personalization, privacy with support information, flexibility with safety consistency, and independence with human assistance. These require governed options rather than one universal mode.

Inclusive defaults reduce request burden and maintenance diversity, yet a default optimized for broad coverage can still exclude people at the tails. Personalization increases fit but introduces configuration, support, testing, and continuity costs. The appropriate portfolio usually combines a well-tested baseline, user-adjustable parameters, a small set of maintained alternative paths, and a governed route for individual exceptions.

More information may help tailor support, but disclosure can create stigma, discrimination, security exposure, and future misuse. Collect functional constraints and preferences at the narrowest useful scope, separate them from unrelated records, and make access visible. If staff need operational instructions, give them the instruction—not necessarily the diagnosis behind it.

Human assistance can restore access quickly and handle ambiguity that automation cannot. It can also reduce privacy, introduce scheduling delay, create dependency, or shift uncompensated work to families and colleagues. Treat assistance as an explicit, resourced mechanism with consent, coverage, training, backup, and boundaries rather than an invisible patch.

Accommodation can impose costs on other users or workers: a schedule change may affect team coordination, an alert may increase sensory load for someone else, or a manual fallback may create staff workload. These conflicts require transparent multi-party design and proportionate burden allocation. They do not justify defaulting to the status quo, whose burdens are often merely less visible.

Failure Modes

Average-user design excludes nonusers. Inherited methods masquerade as essential functions. Accommodation becomes extra coordination work. Burden shifts to families or staff. Alternate modes decay. Supposed equivalence loses time, agency, privacy, or remedy. Representative evidence, essential-function review, explicit ownership, burden measurement, parity testing, and contextual validation mitigate these failures.

Diagnostic failures

Teams may use a diagnosis as a proxy for capacity, test only current successful users, observe a task in ideal conditions, or isolate each demand while missing cumulative load. Detect this when the same label yields inconsistent outcomes, when field performance is worse than laboratory results, or when support and recovery time disappear from the record. Rebuild the profile with contextual ranges, nonusers, peak conditions, and workaround evidence.

Selection failures

A team may choose the first requested tool without exploring system-side changes, optimize cost rather than meaningful equivalence, or impose a “helpful” restriction that removes agency. Detect this through low adoption, persistent workarounds, longer completion, dependence, or user refusal. Reopen the option set, clarify preferences, compare alternatives on outcome and burden, and preserve the right to decline paternalistic solutions.

Implementation failures

Approved accommodations can stall in procurement, arrive without configuration or training, conflict with security policy, fail during handoff, or depend on one knowledgeable employee. Detect missed dates, repeated escalations, configuration drift, and user coordination effort. Give one accountable owner authority across dependencies, publish service targets, maintain configuration records and spares, and test handoffs.

Operational and change failures

Primary systems evolve while alternate paths lag; staffing changes erase informal knowledge; assistive tools update; or a person's capacity and context change. Detect parity defects, rising error, unexplained abandonment, repair recurrence, and divergence after releases. Put alternate paths inside ordinary change control, regression testing, incident review, and lifecycle budgeting.

Recovery failures

A nominal backup may require the same unavailable capacity as the failed path, expose private information, or ask the user to coordinate multiple teams during an outage. Recovery design should specify an accessible notification, a genuinely independent fallback, restoration of state and preferences, escalation authority, maximum outage, and post-incident correction. Rehearse credible combinations such as tool failure plus unavailable specialist support, not only single-component failures.

Neighbor Distinctions

User Context Validation tests assumptions; this pattern redesigns and sustains fit. Cognitive Load Reduction addresses one demand class. Equity Adjustment addresses distributional outcomes. Sociotechnical Integration coordinates subsystems. Physical Constraint Design prevents prohibited action. Human-Capacity Accommodation Design uniquely governs person–task–environment mismatch and equivalent access.

It is also distinct from generic simplification. Simplification removes unnecessary complexity from a task for anyone. Accommodation begins with a specific or representative capacity-demand mismatch and may preserve complexity while changing modality, pacing, sequencing, support, or environment. If plain language or fewer steps fully solves the problem without differentiated paths or ongoing governance, ordinary redesign is enough.

It is not training. Training changes a person's knowledge, skill, or strategy. Accommodation changes the conditions under which existing capability can produce the outcome. Training can be one support mechanism, but it is inappropriate when the demand is unnecessary, the capacity is not trainable within the relevant horizon, or the burden of adaptation should lie with the system. Repeatedly coaching a person around a preventable barrier is workaround institutionalization.

It is not paternalistic restriction. Removing choice, narrowing responsibility, or routing someone into a segregated lower-opportunity path may reduce immediate risk while also reducing autonomy and development. Legitimate safety constraints require evidence, proportionality, exploration of alternative controls, affected-person participation, and review. Protection without those controls is not accommodation design.

Universal design is a close strategy, not a complete synonym. Inclusive defaults can prevent many mismatches before individual disclosure, while accommodation governs residual, conflicting, fluctuating, or uncommon needs and the operational path that sustains them. Ergonomics, accessibility testing, assistive technology, flexible scheduling, and interpretation are mechanisms or domain forms; none alone supplies the entire diagnosis-to-revision structure.

Cross-Domain Examples

A digital service can offer equivalent screen-reader, keyboard, and adjustable-time workflows. A workplace can preserve skilled output through workstation and schedule changes. A public service can provide text, interpretation, asynchronous preparation, and private support rather than one spoken appointment channel.

In education, the essential outcome may be demonstrating analysis rather than handwriting speed or performance in a single timed modality. A capacity-demand analysis can support alternative response modes, bounded extra time, low-distraction settings, accessible materials, assistive compatibility, and equivalent feedback while preserving construct validity and academic standards.

In healthcare, a care pathway can combine accessible communication, lower sensory demand, supported decision-making, flexible appointment length, mobility-compatible facilities, and a documented fallback when interpretation or equipment fails. The design measures clinical outcome, consent, privacy, delay, and caregiver burden rather than merely counting offered services.

In transportation, equivalent trip access requires more than a nominal accessible vehicle. Booking, arrival information, boarding, securement, disruption notice, re-routing, assistance, and complaint resolution must all work under real conditions. Monitoring includes missed trips, extra wait, failure recovery, injury, and dependence on informal help.

In emergency operations, capacity can degrade for everyone through smoke, noise, stress, injury, fatigue, protective equipment, or communication failure. Multimodal alerts, simpler critical choices, accessible evacuation support, redundant channels, protected rest, and rehearsed assistance show how accommodation logic improves population resilience without assuming a permanently labeled user group.

Non-Examples

User interviews without redesign authority, removal of essential safety without an equivalent control, slower stigmatizing paths labeled equivalent, and assistive purchases without integration or maintenance are not complete accommodation design.

A mandatory training course that teaches users to tolerate an unnecessarily confusing interface is not accommodation. A manager informally allowing flexibility while workload and evaluation remain unchanged is not durable accommodation. A separate entrance that is technically usable but locked, remote, or dependent on finding staff is not meaningful equivalence. A medical screening program that sorts people out without redesigning demand is selection, not fit design.

Nor is every preference an accommodation claim that overrides all constraints. The archetype requires a credible capacity-demand relation, an essential outcome, evaluation of affected parties, and proportionate option selection. It can conclude that a requested method is unsafe or infeasible, but only after examining alternative controls and documenting the residual mismatch and review path.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (4)

• Accommodation: Systems modify internal structure or behavior in response to external pressures.
• Adaptive Capacity: Ability to change.
• Human-Centered Accommodation: Adapt to human limits.
• User-Centered Design: Focus on user needs.

Also references 15 related abstractions

• Affordance: An action possibility offered by the fit between an agent and its environment.
• Agency: A system pursues representable goals through actions whose selection is sensitive to its beliefs about its situation, via a goal-representation, world-model, and action-selection coupling.
• Autonomy: A unit's behavior is governed by its own internal rules or chosen reasons rather than external direction, defined by the inner-versus-outer authority asymmetry over a scoped domain.
• Bounded Rationality: Limited decision capacity.
• Cognitive Load: Mental effort.
• Cognitive Resource Depletion: Cognitive capacity degrades from sustained resource consumption.
• Consent: Voluntary agreement.
• Epistemic Justice: Fair knowledge production.
• Equity: Context-sensitive fairness.
• Fault Tolerance: Continue operating under failure.

▸ Show 5 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Digital-Interface Capacity Accommodation · domain variant · recognized

Adapts digital modality, navigation, input, timing, state visibility, cognitive demand, assistive compatibility, and recovery so the complete interaction remains usable.

• Distinct from parent: The parent spans physical, organizational, communication, environmental, and service demands; this variant concentrates the lifecycle on end-to-end digital interaction.
• Use when: A required digital workflow depends on one sensory or motor modality; Timeouts, rapid state change, memory load, or inaccessible recovery create exclusion; Nominal standards conformance does not establish real assistive-technology compatibility; The accessible path repeatedly lags behind changes to the primary interface.
• Typical domains: web services, enterprise software, kiosks, communications, digital identity
• Common mechanisms: person task environment mismatch analysis, multimodal equivalence and assistive compatibility test, accommodation failure and recovery rehearsal

Physical and Ergonomic Task Accommodation · domain variant · recognized

Adapts force, reach, posture, repetition, mobility, environmental exposure, fatigue, tools, sequencing, and recovery while preserving the essential outcome and safety.

• Distinct from parent: This variant prioritizes physical and environmental measurement and may require engineering, facilities, occupational-safety, or equipment mechanisms.
• Use when: A task is possible once but unsafe or unsustainable across its real duration and frequency; Fixed workstation, route, posture, tool, or environmental assumptions exclude capable people; Pain, fatigue, strength, dexterity, mobility, or sensory exposure varies across people or time; Informal coworker assistance conceals a recurring physical-demand mismatch.
• Typical domains: workplaces, products, transportation, facilities, healthcare
• Common mechanisms: person task environment mismatch analysis, essential function and method separation review, accommodation failure and recovery rehearsal

Organizational Schedule and Cognitive Accommodation · governance variant · recognized

Adapts rate, interruption, memory, communication, location, schedule, social exposure, stress, recovery, and support to fluctuating capacity within an organization.

• Distinct from parent: This variant focuses less on a single artifact and more on work allocation, cadence, norms, evaluation, manager capacity, handoff, and protected recovery.
• Use when: Fixed schedules, rapid switching, ambiguous communication, or interruption drive avoidable failure; A flexible policy exists but workload, staffing, evaluation, or manager authority makes it unusable; People must repeatedly disclose needs to different decision makers or renegotiate stable support; Informal colleagues absorb memory, coordination, communication, or coverage work.
• Typical domains: work, education, healthcare, public service, emergency operations
• Common mechanisms: essential function and method separation review, participatory accommodation option workshop, longitudinal fit equity and burden audit

Near names: Accessibility Design, Ergonomic Accommodation, Design for Human Capacity, Adaptive User-Fit Design.