Skip to content

🎨 Palette: Improve accessibility of list action buttons#84

Merged
NSEvent merged 2 commits into
mainfrom
palette-dynamic-accessibility-labels-3556881315248094765
Jul 13, 2026
Merged

🎨 Palette: Improve accessibility of list action buttons#84
NSEvent merged 2 commits into
mainfrom
palette-dynamic-accessibility-labels-3556881315248094765

Conversation

@NSEvent

@NSEvent NSEvent commented Jul 12, 2026

Copy link
Copy Markdown
Owner

💡 What: Added dynamic item names to the .help() and .accessibilityLabel() strings for list row action buttons (Edit, Delete, Clear) in MacroListView, ChordSequenceListViews, GestureListViews, and ScriptListView.
🎯 Why: Previously, VoiceOver would just read "Edit" or "Delete" identically for every row, making it impossible for visually impaired users to know which list item they were operating on. Adding the name provides necessary context.
♿ Accessibility: Major VoiceOver improvement for all main list interfaces, disambiguating repeated action buttons.


PR created automatically by Jules for task 3556881315248094765 started by @NSEvent

Summary by CodeRabbit

  • Accessibility

    • Updated edit, delete, clear, and shared-library action labels with item-specific names.
    • Added contextual tooltips for macros, chords, sequences, gestures, and scripts.
    • Added fallback labels such as “Unnamed Macro” and “Untitled Script” when names are blank.
  • Documentation

    • Added guidance for using dynamic labels and tooltips on repeated icon-only list actions.

Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@NSEvent, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9933c690-e747-4db6-9fe8-088b1308c042

📥 Commits

Reviewing files that changed from the base of the PR and between 7c51c48 and 1eb5dca.

📒 Files selected for processing (1)
  • XboxControllerMapper/XboxControllerMapper/Views/MainWindow/ChordSequenceListViews.swift
📝 Walkthrough

Walkthrough

SwiftUI icon-only list actions now provide contextual .help() and .accessibilityLabel() strings using macro, script, chord, sequence, and gesture names, with fallbacks for unnamed macros and scripts. Documentation records the dynamic-labeling convention.

Changes

Dynamic accessibility labels

Layer / File(s) Summary
Macro and script action labels
.Jules/palette.md, XboxControllerMapper/XboxControllerMapper/Views/Macros/MacroListView.swift, XboxControllerMapper/XboxControllerMapper/Views/Scripts/ScriptListView.swift
Macro and script edit/delete controls now include item names in help text and accessibility labels, using fallback names when necessary.
Main window row action labels
XboxControllerMapper/XboxControllerMapper/Views/MainWindow/ChordSequenceListViews.swift, XboxControllerMapper/XboxControllerMapper/Views/MainWindow/GestureListViews.swift
Chord, sequence, and gesture edit, delete, and clear controls now include contextual names in help text and accessibility labels.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: improving accessibility text for list action buttons across the UI.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch palette-dynamic-accessibility-labels-3556881315248094765

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@XboxControllerMapper/XboxControllerMapper/Views/MainWindow/ChordSequenceListViews.swift`:
- Around line 118-127: Update the context-menu action Label strings in the row
views, including the additional sequence-action block, to include the associated
chord or sequence name just like the trailing buttons. Use a suitable fallback
when the name is empty, while preserving the existing action titles and
behavior.

In
`@XboxControllerMapper/XboxControllerMapper/Views/MainWindow/GestureListViews.swift`:
- Around line 81-91: Update the context-menu accessibility Label strings for the
edit and clear actions in the gesture row to include gestureType.displayName,
matching the contextualized .help and .accessibilityLabel values while
preserving the existing action behavior.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 08f90e4c-9314-450d-bcc9-eb786169aca3

📥 Commits

Reviewing files that changed from the base of the PR and between c431981 and 7c51c48.

📒 Files selected for processing (5)
  • .Jules/palette.md
  • XboxControllerMapper/XboxControllerMapper/Views/Macros/MacroListView.swift
  • XboxControllerMapper/XboxControllerMapper/Views/MainWindow/ChordSequenceListViews.swift
  • XboxControllerMapper/XboxControllerMapper/Views/MainWindow/GestureListViews.swift
  • XboxControllerMapper/XboxControllerMapper/Views/Scripts/ScriptListView.swift

Comment on lines +81 to +91
.help("Edit \(gestureType.displayName)")
.accessibilityLabel("Edit \(gestureType.displayName)")

if mapping?.hasAction == true {
Button(action: onClear) {
Image(systemName: "trash")
.foregroundColor(.red.opacity(0.8))
}
.buttonStyle(.borderless)
.help("Clear")
.accessibilityLabel("Clear")
.help("Clear \(gestureType.displayName)")
.accessibilityLabel("Clear \(gestureType.displayName)")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Contextualize the gesture context-menu actions too.

The new icon-button labels include the gesture name, but the context menu still announces generic “Edit Gesture” and “Clear Action” labels. Include gestureType.displayName in those Label strings so the contextual accessibility behavior is consistent across all row actions.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@XboxControllerMapper/XboxControllerMapper/Views/MainWindow/GestureListViews.swift`
around lines 81 - 91, Update the context-menu accessibility Label strings for
the edit and clear actions in the gesture row to include
gestureType.displayName, matching the contextualized .help and
.accessibilityLabel values while preserving the existing action behavior.

…pilation)

Co-authored-by: NSEvent <44446865+NSEvent@users.noreply.github.com>
@NSEvent NSEvent merged commit 8821423 into main Jul 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant