A message can arrive without its meaning¶
Cross-Domain EchoesShared pattern · Interface
A screen may show a heading or an error clearly while exposing none of that meaning to a screen reader. A request for a “generator” can also arrive intact at another agency yet fail to specify the power output the incident requires. Both failures occur at an interface: a signal crosses the boundary, but the receiver lacks the structure needed to act on it. The repair is to make the relevant meaning explicit in the exchanged representation. Accessibility requires machine-readable roles, states and associations; mutual aid requires capability definitions. Neither visual polish nor successful delivery of a label establishes a usable exchange.
Choose a role to see its counterpart in both examples. The diagrams show relationships, not measured quantities.
Accessibility engineering
Meaning exposed to assistive technology
Read Screen-Reader AmbiguityDomain-specific abstraction
Visual organization must be represented in the semantic layer consumed by assistive technology.
In this example: A visually correct interface can still expose incorrect roles, names, state or associations.
Incident resource coordination
Capability exposed to a requesting agency
Read Resource-Typing MismatchDomain-specific abstraction
Resource requests need capability specifications that travel consistently across organizations.
In this example: Matching a resource name does not establish adequate capacity, certification or readiness.
The contract exposes the distinctions that affect valid use.
Written comparison
Meaning needed by the receiver
Accessibility engineering
Role, state and association
Incident resource coordination
Operational capability
The receiver needs actionable structure beyond a visible or transmitted name.
An explicit exchange contract
Accessibility engineering
Machine-readable semantics
Incident resource coordination
Capability parameters and type
The contract exposes the distinctions that affect valid use.
A receiver-side check
Accessibility engineering
Assistive-technology testing
Incident resource coordination
Capability-to-need comparison
A check must examine what the receiver actually obtains; successful transmission is insufficient.
What carries across
Test what the receiver can infer from the exposed contract, not merely whether a label or signal arrived.
Where the comparison stops
The shared interface failure is missing operational meaning. Software semantic trees and institutional capability catalogs repair it through different systems.
- Accessibility semantics are not equipment capacity; their validation methods differ.
- An accurately typed resource may still be unavailable or unsuitable for other reasons.
- Semantic encoding supports accessible use but does not by itself establish every usability property.
Conditions for this comparison
- The visual meaning has an accessible machine-readable counterpart.
- Agencies share and apply the same resource-capability definitions.
Source entries
Shared pattern
Interface
Prime
Core Idea
A bounded surface—physical, digital, or abstract—across which two distinct systems exchange information, energy, matter, or control, the foundational concept Parnas (1972) crystallized in his analysis of modular decomposition. An interface is not merely a boundary; it is a contract specifying what gets exposed, what remains hidden, what signals cross, and what guarantees hold on each side, as Liskov and Zilles (1974) formalized in their treatment of abstract data types.
Accessibility engineering
Screen-Reader Ambiguity
Domain-specific abstraction
Core Idea
The corresponding intervention family is authoring and maintaining the semantic layer: semantic HTML element choice over styled divs, ARIA role and property annotation where native semantics are insufficient, programmatic name and state exposure in native frameworks, tagged structure in document formats. The diagnostic method is accessibility-tree inspection and assistive-technology testing, not visual review.
Incident resource coordination
Resource-Typing Mismatch
Domain-specific abstraction
Core Idea
the labels used to request and deliver resources through the mutual-aid system do not pin down the operational capability that the requesting commander actually needs.