FA-54235 / Accessibility interaction semantics / Member archive

Routing offsets are incorrectly translated as document cell offsets · case 05

Routing offsets are incorrectly translated as document cell offsets.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Input [cells,offset,width,route] where cells [source_start,source_end,content,editable]. Clip display window by nonnegative offset and width. Each cell has one display position regardless of content length. Routing uses a zero-based position inside displayed cells; return None if outside window or cell not editable, otherwise [source_start,source_end]. Display contents replace empty cell content with a space; protected content (exact token SECRET) displays a bullet. Return [display,source_ranges,route_result,has_previous,has_next]. Source ranges preserve zero-width insertion cells.

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	`[["\u2022", " "], [[5, 7], [7, 7]], null, true, false]`	`[["\u2022", " "], [[5, 7], [7, 7]], [7, 7], 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.