Fix dark button hover contrast - #621
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Independent review: LGTM — no blocking findings. I verified the exact base-to-head diff is limited to the shared default Button dark-hover opacity, its Storybook hover assertion, and matching LAT documentation. The change raises the dark hover foreground contrast from ~3.87:1 to ~4.65:1 while preserving the light hover and every other variant. The exact Storybook contrast suite passed once plus five repeated runs (10/10 tests), |
d6316c1
into
codex/ui-page-coverage-start-crew
What changed
bg-primary/80tobg-primary/90Why
The dark default Button combined
text-primary-foregroundwithdark:hover:bg-primary/80, producing only 3.85:1 contrast for normal text. The 90% hover background preserves the interaction treatment while raising the pair above WCAG AA.Light hover behavior and all other Button variants are unchanged.
Validation
confirmation trigger hover (dark)failed at 3.85:1@repo/ui: 25 tests, typecheck, build, focused Biomelat checkStack
Base:
codex/ui-page-coverage-start-crewmainSummary by cubic
Fix dark theme default Button hover contrast to meet WCAG AA. Raises hover background to
bg-primary/90and adds an explicit hover audit in Storybook.dark:hover:bg-primary/80todark:hover:bg-primary/90; light and other variants unchanged.Written for commit 1edf638. Summary will update on new commits.