marcel/familienarchiv
1
0
Fork 0
Code Issues 118 Pull Requests 2 Actions 4 Packages Projects Releases Wiki Activity

feat(documents): keyboard-accessible range zoom for timeline #479

New Issue
Open
opened 2026-05-08 10:12:06 +02:00 by marcel · 0 comments
marcel commented 2026-05-08 10:12:06 +02:00
Owner
Copy Link

Context

Spun out of PR #478 (issue #385). Leonie's review flagged that the drag-to-zoom gesture on the timeline density widget has no keyboard equivalent, which is a WCAG 2.1.1 (Keyboard) failure: keyboard users can only single-click a bar (filter only) and cannot trigger the range-zoom flow that mouse and touch users get.

"Drag is genuinely hard to keyboard-equivalent, but the feature it enables (range zoom) cannot be keyboard-only-blocked."
— Leonie, on PR #478

Acceptance criteria

  • Pressing Shift+Click (or Shift+Enter / Shift+Space on a focused bar) extends the selection from the previously focused/clicked bar to the current one and commits zoom + filter atomically (the same payload as triggerSearchWithZoom).
  • The gesture is announced to assistive technology via the existing timeline_dragging_aria_live polite live region (or an equivalent confirmation message).
  • An onboarding affordance — a title tooltip or a one-time hint — explains the keyboard shortcut so it's discoverable.
  • The existing single-click (filter only) and pointer-drag (range zoom) flows are unchanged.

Out of scope

  • Touch-equivalent gesture (already covered by drag).
  • Reorganising the bar layout for tablet (covered by the separate tablet-breakpoint follow-up).

Test plan

  • Component unit test: pressing Shift+Click on a second bar after a normal click on a first bar emits both zoomFrom/zoomTo and from/to.
  • Component unit test: Shift+Enter on a focused bar after a previous focus extends and commits.
  • E2E (deferred to the Playwright follow-up): full URL update verification.

Related

## Context Spun out of [PR #478](http://heim-nas:3005/marcel/familienarchiv/pulls/478) (issue #385). Leonie's review flagged that the drag-to-zoom gesture on the timeline density widget has no keyboard equivalent, which is a WCAG 2.1.1 (Keyboard) failure: keyboard users can only single-click a bar (filter only) and cannot trigger the range-zoom flow that mouse and touch users get. > "Drag is genuinely hard to keyboard-equivalent, but the *feature it enables* (range zoom) cannot be keyboard-only-blocked." > — Leonie, on PR #478 ## Acceptance criteria - [ ] Pressing **Shift+Click** (or **Shift+Enter** / **Shift+Space** on a focused bar) extends the selection from the previously focused/clicked bar to the current one and commits zoom + filter atomically (the same payload as `triggerSearchWithZoom`). - [ ] The gesture is announced to assistive technology via the existing `timeline_dragging_aria_live` polite live region (or an equivalent confirmation message). - [ ] An onboarding affordance — a `title` tooltip or a one-time hint — explains the keyboard shortcut so it's discoverable. - [ ] The existing single-click (filter only) and pointer-drag (range zoom) flows are unchanged. ## Out of scope - Touch-equivalent gesture (already covered by drag). - Reorganising the bar layout for tablet (covered by the separate tablet-breakpoint follow-up). ## Test plan - Component unit test: pressing Shift+Click on a second bar after a normal click on a first bar emits both `zoomFrom`/`zoomTo` and `from`/`to`. - Component unit test: Shift+Enter on a focused bar after a previous focus extends and commits. - E2E (deferred to the Playwright follow-up): full URL update verification. ## Related - Parent issue: #385 - Parent PR: #478 (deferred this scope per Felix's discussion with the user) - Sibling follow-up: `test(documents): timeline density Playwright coverage`
marcel added the featureui labels 2026-05-08 10:12:27 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label feature ui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#479
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?