humanspeak / svelte-virtual-list / 28655041441

72%

main: 72%

push

github

feat(virtual-list): keyboard-accessible viewport with labeled region (#419)

* test(virtual-list): add failing spec for keyboard viewport accessibility (#414)

Fixture at /tests/issues/issue-414 with live red/green stats probing
three things: focus() actually landing on the viewport, role/aria-label
semantics for assistive tech, and an 8-key scroll matrix (ArrowUp/Down,
PageUp/Down, Space, Shift+Space, Home, End) driven by synthetic
KeyboardEvents from a mid-list position. Synthetic keys are untrusted
so browsers never natively scroll from them — every key probe measures
the component's own keydown handler, deterministically across engines.
The scroll-settle helper polls scrollTop to stability so the probes are
agnostic to instant vs smooth scrolling.

Pre-fix state captures the cross-engine inconsistency the issue is
about: on chromium the focusable probe passes (Chrome natively focuses
scrollable divs) while semantics and all 8 keys fail; on webkit even
focusable fails (Safari does not focus scrollable divs). 5 of 6 specs
failing across the two engines.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* feat(virtual-list): keyboard-accessible viewport with labeled region (#414)

The viewport was a bare overflow-y: scroll div: keyboard users could
only operate it where the browser happens to make scrollable divs
focusable (Chrome/Firefox do, Safari does not), and assistive tech
announced an unlabeled group.

The viewport now renders as a focusable labeled region — role="region",
tabindex="0", and a configurable viewportLabel prop (default
'Scrollable list') — and owns the standard scroll keys itself so the
behavior is identical on every engine: arrows move a line (40px),
PageUp/PageDown and Space/Shift+Space move a page (viewport height
minus one line of overlap), Home/End jump to the edges. Handled keys
preventDefault so Space cannot page the document; keys are only claimed
when the viewport itself is focused, so interactive item content
(bu... (continued)

447 of 680 branches covered (65.74%)

Branch coverage included in aggregate %.

26 of 37 new or added lines in 2 files covered. (70.27%)

822 of 1071 relevant lines covered (76.75%)

423.78 hits per line