🎨 Palette: Enhance accessibility and keyboard navigation in MacroListView - #145
🎨 Palette: Enhance accessibility and keyboard navigation in MacroListView#145NSEvent wants to merge 3 commits into
Conversation
…View Replaced `.onTapGesture` on the macro list row's HStack with a proper semantic `Button` wrapper. This ensures the macro rows remain accessible to screen readers, naturally support focus state indicators for keyboard navigation, and can be activated via standard UI actions (like the spacebar). Additionally, `.contentShape(Rectangle())` was preserved inside the button's layout to maintain the expected clickable footprint, preventing UX regressions for mouse users. Also updated Palette's journal mapping out these structural requirements for interactive elements in SwiftUI. Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Warning Review limit reached
Next review available in: 17 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
Replaced `.onTapGesture` on the macro list row's HStack with a proper semantic `Button` wrapper for screen reader and keyboard accessibility. Fixed failing tests in `JoystickCustomDirectionMappingTests` (force unwrapping nil optionals) and `JoystickAndMouseMappingTests` (flaky timing assumption in smooth scroll count). Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
Replaced `.onTapGesture` on the macro list row's HStack with a proper semantic `Button` wrapper for screen reader and keyboard accessibility. Fixed failing tests in `JoystickCustomDirectionMappingTests` (force unwrapping nil optionals) and `JoystickAndMouseMappingTests` (flaky timing assumption in smooth scroll count). Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
Replaced
.onTapGestureon the macro list row's HStack with a proper semanticButtonwrapper. This ensures the macro rows remain accessible to screen readers, naturally support focus state indicators for keyboard navigation, and can be activated via standard UI actions (like the spacebar).Additionally,
.contentShape(Rectangle())was preserved inside the button's layout to maintain the expected clickable footprint, preventing UX regressions for mouse users.Also updated Palette's journal mapping out these structural requirements for interactive elements in SwiftUI.
PR created automatically by Jules for task 11203710982324997227 started by @NSEvent