Skip to content

🎨 Palette: Improve New Agent modal accessibility - #72

Open
parvezk wants to merge 1 commit into
mainfrom
palette/a11y-new-agent-modal-11105085101077024814
Open

🎨 Palette: Improve New Agent modal accessibility#72
parvezk wants to merge 1 commit into
mainfrom
palette/a11y-new-agent-modal-11105085101077024814

Conversation

@parvezk

@parvezk parvezk commented Jul 28, 2026

Copy link
Copy Markdown
Owner

💡 What

This PR adds comprehensive accessibility improvements to the "New Agent" modal component in the web interface.

🎯 Why

Several interactive elements in the NewAgentModal lacked proper ARIA roles and keyboard accessibility styling, making them difficult to use for users relying on screen readers or keyboard navigation. The vendor selection used custom div/button combinations without native radio semantics, and several text inputs relied solely on placeholders for context.

♿ Accessibility Improvements

  • Added explicit role="radiogroup" and role="radio" with aria-checked states to the custom vendor tiles.
  • Associated the vendor group label using aria-labelledby.
  • Connected the "Task" label directly to its textarea using htmlFor and id.
  • Added missing aria-labels to the repo and branch inputs.
  • Implemented focus-visible styling on the vendor tiles so keyboard users can clearly see which item is focused.

PR created automatically by Jules for task 11105085101077024814 started by @parvezk

- Add `role="radiogroup"`, `role="radio"`, and `aria-checked` to the custom vendor selection buttons
- Map the explicit `id` of the vendor label to `aria-labelledby` on the radiogroup
- Associate the "Task" label with the `<Textarea>` using `htmlFor` and `id`
- Add explicit `aria-label`s to the repository and branch inputs which only had placeholders
- Add `focus-visible` ring styling to the vendor radio buttons for better keyboard navigation

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@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.

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
polyagent Ready Ready Preview, Comment Jul 28, 2026 8:11am

@cursor

cursor Bot commented Jul 28, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0220c1b1d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +111 to 113
role="radio"
aria-checked={selected}
onClick={() => setVendor(v)}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Add radio-group keyboard behavior

When a keyboard or screen-reader user reaches this newly declared radio group, the expected interaction is to keep one radio in the Tab sequence and use the Arrow keys to move focus and select an option. These buttons have neither roving tabIndex nor an onKeyDown handler, so every option remains a Tab stop and the Arrow keys announced for a radio group do nothing; implement arrow-key focus/selection or retain button semantics/use native radio inputs.

Useful? React with 👍 / 👎.

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