FA-54037 / Accessibility interaction semantics / Member archive

Repeated semantic children occupy multiple page slots · case 02

Repeated semantic children occupy multiple page slots.

Member previewVariant 2 · 3 implementations · 10 checks per implementation

Case contract

Input [children,start,count,revision,requested_revision,exposed_ids]. Page accessibility child descriptors in source order, first dedupe IDs then filter exposed IDs. start/count must be nonnegative integers excluding booleans; invalid returns {error:range}. Stale requested revision returns {error:stale} before range checks. Return children slice, total exposed unique count, next offset or None, revision. Zero count yields empty page with next None to avoid nonprogress. Start beyond total gives empty and next None.

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	`{"children": ["a", "b"], "next": 2, "revision": 2, "total": 4}`	`{"children": ["a", "b"], "next": 2, "revision": 2, "total": 3}`	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.