Skip to content

🎨 Palette: Add accessible clear buttons to search inputs#124

Closed
schmug wants to merge 1 commit into
mainfrom
ux/add-accessible-clear-buttons-1057004159306697568
Closed

🎨 Palette: Add accessible clear buttons to search inputs#124
schmug wants to merge 1 commit into
mainfrom
ux/add-accessible-clear-buttons-1057004159306697568

Conversation

@schmug
Copy link
Copy Markdown
Owner

@schmug schmug commented May 16, 2026

πŸ’‘ What: Added an accessible 'clear' (X) button to the search and filter inputs across the application (Launcher, ProjectsApp, and BlogApp).

🎯 Why: When users are typing a long search query and want to start over, it's cumbersome to manually highlight and delete the text. Providing a clear button improves efficiency. Managing focus to return to the input upon clearing ensures continuous, accessible keyboard interaction.

πŸ“Έ Before/After:
The clear button appears only when there is input text. It uses the lucide-react X icon and aligns neatly inside the input container.

β™Ώ Accessibility:

  • Added aria-label="Clear search" for screen readers.
  • Ensured keyboard accessibility with focus-visible ring styling.
  • Restores focus to the search input element when clicked, allowing users to keep typing immediately.
  • Added type="button" to ensure it doesn't accidentally trigger a form submission.

PR created automatically by Jules for task 1057004159306697568 started by @schmug

- Added 'X' clear buttons to search inputs in Launcher, ProjectsApp, and BlogApp.
- Ensured keyboard accessibility and focus management by restoring focus to the input upon clearing.
- Added explicit `type="button"` and `aria-label="Clear search"` attributes.
- Utilized existing CSS design tokens for focus-visible states.

Co-authored-by: schmug <38227427+schmug@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.

@schmug
Copy link
Copy Markdown
Owner Author

schmug commented May 16, 2026

Superseded by #127 (merged to main), which consolidated the best of the duplicate Bolt/Sentinel/Palette scheduled-agent PRs into one reviewed change. Closing as duplicate.

@schmug schmug closed this May 16, 2026
@google-labs-jules
Copy link
Copy Markdown
Contributor

Superseded by #127 (merged to main), which consolidated the best of the duplicate Bolt/Sentinel/Palette scheduled-agent PRs into one reviewed change. Closing as duplicate.

Understood. Acknowledging that this work is superseded by #127 and stopping work on this task.

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