FA-54265 / Accessibility interaction semantics / Member archive

Controlled objects report forward control instead of controller relation · case 05

Controlled objects report forward control instead of controller relation.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Input [node_ids,relations] relations [source,kind,target]. Kind label_for maps inverse labelled_by, description_for maps described_by, controls maps controlled_by, details maps details_for. Unknown types ignored. Resolve only existing distinct nodes. For each node output direct and inverse [kind,other_id] pairs, deduping while preserving relation encounter order. Direct is appended before inverse. Nodes with no links are retained in input order; input node IDs are unique. Forward and reverse kinds remain distinct even for reciprocal declarations.

Why this case matters

Offline accessibility bridge model with explicit policy; useful for testing semantic API adapters independently of browser implementations.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
contract fixture 1	`[["a", [["label_for", "b"], ["description_for", "b"], ["details", "5"]]], ["b", [["labelled_by", "a"], ["described_by", "a"], ["controls", "5"]]], ["5", [["controls", "b"], ["details_for", "a"]]], ["alone", []]]`	`[["a", [["label_for", "b"], ["description_for", "b"], ["details", "5"]]], ["b", [["labelled_by", "a"], ["described_by", "a"], ["controls", "5"]]], ["5", [["controlled_by", "b"], ["details_for", "a"]]], ["alone", []]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.