Skip to content

🎨 Palette: Improve accessibility of New Agent form - #80

Open
parvezk wants to merge 1 commit into
mainfrom
palette-a11y-new-agent-form-12531572640638336225
Open

🎨 Palette: Improve accessibility of New Agent form#80
parvezk wants to merge 1 commit into
mainfrom
palette-a11y-new-agent-form-12531572640638336225

Conversation

@parvezk

@parvezk parvezk commented Jul 30, 2026

Copy link
Copy Markdown
Owner

💡 What: Added essential accessibility attributes to the New Agent Modal form.
🎯 Why: The custom vendor selection UI was built using un-semantic div and button elements acting as a radio group, which screen readers couldn't properly interpret. Furthermore, several form inputs lacked explicit association with their text labels, making navigation difficult for assistive technologies.
📸 Before/After: Screen readers will now announce the vendor selection as a radio group with checked/unchecked states, and all inputs will have correctly announced labels when focused.
♿ Accessibility:

  • Added role="radiogroup" to the vendor container.
  • Added role="radio" and aria-checked to the vendor buttons.
  • Added explicit id and htmlFor pairings for Repo, Model, and Task inputs.
  • Added an aria-label to the branch input.

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

Add ARIA roles (`radiogroup`, `radio`) and `aria-checked` states to the custom vendor selection buttons.
Associate all form labels with their corresponding inputs (Repo, Model, Task) using `htmlFor` and `id` attributes.
Add an `aria-label` to the branch input which lacks a visible label.
Add a new learning to the Palette journal regarding these accessibility requirements.

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 30, 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 Jul 30, 2026 8:00am

@cursor

cursor Bot commented Jul 30, 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: 995b0fa42d

ℹ️ 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 Implement the keyboard behavior promised by the radio roles

For keyboard-only users, these elements now expose themselves as a radio group, but they retain ordinary button behavior: every option remains in the Tab sequence, and Arrow keys do not move selection within the group. Add roving tabIndex and Arrow-key handling, or use native radio inputs, so the interaction matches the announced radio semantics.

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