Skip to content

Fix DatePicker segment sizing and Dropdown focus visibility - #255

Merged
woksin merged 1 commit into
mainfrom
fix/datepicker-dropdown-accessibility
Sep 9, 2026
Merged

Fix DatePicker segment sizing and Dropdown focus visibility#255
woksin merged 1 commit into
mainfrom
fix/datepicker-dropdown-accessibility

Conversation

@woksin

@woksin woksin commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Two accessibility fixes: date picker segments that were too small to hit reliably, and dropdown options that painted a browser-default focus outline instead of the Cratis focus ring.

Fixed

DatePicker segments could shrink below a usable hit target and overflow
their input at narrow widths (e.g. a 343px phone column) with 12-hour
time enabled; wrap the input and give each segment a minimum 24px box.

Dropdown options lacked a visible keyboard focus ring, and the
focus-visible outline could lose to the selected-option background.
Add a themed focus-visible box-shadow ordered after the selected rule,
keep the existing forced-colors outline, and add a spec pinning the
CSS cascade order plus the forced-colors contract.

Update the story-count ratchet and matrix log for the four added
accessibility stories, and derive the matrix's logged story count from
the verified index instead of a second hardcoded literal.

Refs #238, #240
@woksin woksin added the patch label Sep 9, 2026
@woksin
woksin merged commit 761c686 into main Sep 9, 2026
43 of 44 checks passed
@woksin
woksin deleted the fix/datepicker-dropdown-accessibility branch September 9, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant