FA-53518 / Accessibility interaction semantics / Member archive

Revealed values lose their protected semantic flag · case 03

Revealed values lose their protected semantic flag.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Input [raw,protected,reveal,permission,readonly,multiline,max_length,placeholder]. Raw is a string; max_length is None or nonnegative. Normalize CRLF before applying codepoint cap. In single line replace LF with space. Protected text reveals only when reveal and permission; otherwise one bullet per capped codepoint excluding LF, which is retained. Empty values retain empty text and expose placeholder separately. Return {text,placeholder,length,editable,protected}; length is the length after cap, editable is not readonly, protected reports input flag even when revealed.

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
reveal lacks permission	`{"editable": true, "length": 3, "placeholder": "", "protected": false, "text": "\u2022\u2022\u2022"}`	`{"editable": true, "length": 3, "placeholder": "", "protected": true, "text": "\u2022\u2022\u2022"}`	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.