FA-54005 / Accessibility interaction semantics / Member archive

Rejected semantic patches consume revision numbers · case 05

Rejected semantic patches consume revision numbers.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Input [initial,revision,updates]. Updates [base_revision,next_revision,changes] apply atomically only if base matches current and next is greater; updates cannot change immutable id or role. Allowed dynamic keys name,description,value,help,language; unknown keys reject whole update. None deletes a property, empty string is retained; values must be strings or None. Return [state,revision,accepted_flags]. Copy initial. Revision advances even for no-op changes.

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	`[{"help": "", "id": "x", "name": "new", "role": "image"}, 7, [true, false]]`	`[{"help": "", "id": "x", "name": "new", "role": "image"}, 6, [true, false]]`	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.