Interface Accessibility & Navigation Failures

← Back to Domain-Specific Families

Abstractions about interface states and design failures that impair orientation, control, visibility, and accessible interaction. They include empty states, focus order, keyboard and screen-reader traps, ambiguous labels and microcopy, layout breakage, mode errors, navigation loops, and wayfinding.

18 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Empty State Design — The UI practice of deliberately designing the zero-content view — treating it as a first-class state with a fixed four-slot template (message, intentionality cue, call-to-action, optional sample) rather than whatever the populated layout degrades to.
• Empty-State Failure — The interface condition in which a view has no content and provides no scaffolding for the absence — no explanation of the cause, no disambiguation among the possible causes (new, filtered, permission, loading, error), and no next action — so the user, left to infer meaning from nothing, typically concludes wrongly that the system is broken or gated.
• Focus-Order Failure — The accessibility defect in which an interface advances programmatic focus (Tab navigation, screen-reader linearization) in a sequence that diverges from the task's semantic order — invisible to visual review, and sometimes placing a confirmation control before the content it confirms.
• Hidden Label — A string attached to a controlled-vocabulary concept that is indexed for retrieval but withheld from display — so a user typing a typo, deprecated synonym, or embarrassing prior name finds the concept while the result still shows only the sanctioned preferred term.
• Implicit Animation — A user-interface animation method in which a change to an animatable property or declared target state triggers the framework to synthesize, schedule, and manage the visual transition under an attached policy, without application code explicitly starting and controlling a timeline for that occurrence.
• Information-Scent Failure — Diagnose a navigation failure as the surface cues a user reads before clicking — link text, labels, snippets — failing to predict the destination's content, so the user invests a click on a wrong prediction and backtracks, hunts, or abandons.
• Keyboard Accessibility — The design property that every interactive function in a GUI can be operated with the keyboard alone — making the keyboard a channel-redundant, complete alternative to the pointer, and the upstream contract every assistive technology depends on.
• Keyboard Trap — The accessibility failure where a keyboard-only user moves focus into a UI element that receives focus but never yields it — an absorbing state in the focus-navigation graph, invisible to mouse users because a click supplies the exit edge they lack.
• Microcopy Ambiguity — The HCI failure where a terse interface label admits more than one reading, so the user decompresses it against a prior different from the designer's and acts correctly on the wrong interpretation.
• Mode Error — The interaction failure in which the same user action is interpreted differently by a system depending on a hidden mode the user does not perceive — the user acts correctly for the mode they believe is active, and the system, in the actually active mode, does something else.
• Navigation loop — Diagnose a workflow where a user cannot reach their goal by modeling the interface as a directed graph and asking one structural question — is any goal state reachable from the current state? — rather than blaming screen quality or user confusion.
• Orientation Loss — Diagnose why a competent user gets lost by checking three location facts — where am I, what can I move to, how did I arrive — at each transition seam, reading the orientation state off the count of missing facts regardless of substrate.
• Responsive-Layout Breakage — Diagnose the silent UI failure where an interface's content survives a viewport, device, or locale transformation but its layout-encoded meaning — priority, adjacency, hierarchy, above-the-fold prominence — is lost, so a passing content-accessibility check actively conceals the defect.
• Robust Accessibility — Author web content so its load-bearing meaning lives in structural markup and the accessibility tree rather than in presentational accidents, so any current or future assistive technology — including ones the author cannot test against — can recover the intent through the same shared API.
• Screen-Reader Ambiguity — An interface's visual structure carries semantic information never encoded into the machine-readable accessibility tree, so an assistive-technology user — navigating only that projection — encounters an interface stripped of the organization a sighted user relies on.
• Virtual Desktop — Expand a graphical workspace beyond one physical screen by retaining windows in multiple switchable contexts or in a larger logical surface and exposing only the selected viewport at a time.
• Visibility of System Status — Keep users out of the dark by making a system's hidden internal state externally legible through timely, appropriately calibrated feedback — enumerating every state a user's actions can induce and asking, for each, whether the user can see they are in it in time to choose a next action.
• Wayfinding System — A designed network of environmental cues on a legible substrate that lets a goal-directed agent localise, choose a next step, and recover from disorientation — pushing navigation work out of the head into the environment.