FA-54308 / Accessibility interaction semantics / Member archive

Added objects ignore declared semantic sibling order · case 03

Added objects ignore declared semantic sibling order.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Input [before,after] maps stable object ID to {role,name,parent,order}. Return delta operations in phases: removed IDs sorted lexical; added IDs sorted by after order then ID; common IDs sorted lexical get role-replace if role differs, otherwise name-set if name differs; parent/order changes append move even after role-replace. Removed values use old role, added records preserve complete new record, name-set preserves empty names. Same ID is never remove+add just for role changes. Return operations lists.

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 4	`[["add", "a", {"name": "A", "order": 1, "parent": null, "role": "group"}], ["add", "z", {"name": "Z", "order": 0, "parent": null, "role": "image"}]]`	`[["add", "z", {"name": "Z", "order": 0, "parent": null, "role": "image"}], ["add", "a", {"name": "A", "order": 1, "parent": null, "role": "group"}]]`	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.