Skip to content

Comments

🎨 Palette: Improve accessibility of chat controls#91

Draft
Dexploarer wants to merge 1 commit intodevelopfrom
palette-accessibility-chatview-5106433068055661388
Draft

🎨 Palette: Improve accessibility of chat controls#91
Dexploarer wants to merge 1 commit intodevelopfrom
palette-accessibility-chatview-5106433068055661388

Conversation

@Dexploarer
Copy link
Owner

Improved accessibility of the ChatView component by adding missing ARIA labels and attributes.

Changes:

  • Added aria-label to:
    • Avatar toggle button ("Hide avatar" / "Show avatar")
    • Mute/Unmute button ("Unmute agent voice" / "Mute agent voice")
    • Voice input (Mic) button ("Stop listening" / "Voice input")
    • Send button ("Sending message" / "Send message")
    • Textarea input ("Message input")
  • Added type="button" to all buttons to prevent accidental form submissions.
  • Added aria-hidden="true" to SVGs inside buttons.

Verification:

  • Verified using a Playwright script that checks for the presence of these attributes in the rendered DOM.
  • Visually verified that the UI layout remains unchanged.

PR created automatically by Jules for task 5106433068055661388 started by @Dexploarer

- Add `aria-label` to avatar toggle, mute toggle, and mic buttons.
- Add `type="button"` to all interactive buttons to prevent accidental form submission.
- Add `aria-hidden="true"` to icon SVGs to improve screen reader experience.
- Add `aria-label` to the main chat textarea.
- Add dynamic `aria-label` to the Send button to indicate sending state.
@google-labs-jules
Copy link

👋 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.

@github-actions github-actions bot added the ui label Feb 18, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 18, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch palette-accessibility-chatview-5106433068055661388

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 and usage tips.

Comment on lines 350 to 358
if (muting) voice.stopSpeaking();
}}
title={agentVoiceMuted ? "Unmute agent voice" : "Mute agent voice"}
aria-label={agentVoiceMuted ? "Unmute agent voice" : "Mute agent voice"}
>
<svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round">
<svg aria-hidden="true" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round">
<polygon points="11 5 6 9 2 9 2 15 6 15 11 19 11 5" />
{agentVoiceMuted ? (
<line x1="23" y1="9" x2="17" y2="15" />

Choose a reason for hiding this comment

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

The mute/unmute button calls voice.stopSpeaking() immediately when muting. If voice.stopSpeaking() is asynchronous or has side effects, rapid toggling could cause race conditions or inconsistent state.

Recommendation:

  • Ensure voice.stopSpeaking() is idempotent and safe to call multiple times in quick succession.
  • If it is asynchronous, consider debouncing the button or disabling it while the operation is in progress to prevent overlapping calls.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dexploarer, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the accessibility of the chat interface by incorporating crucial ARIA attributes and proper button typing. These changes ensure that users relying on assistive technologies can more effectively navigate and interact with the chat controls, leading to a more inclusive user experience without altering the visual layout.

Highlights

  • Accessibility Improvements: Added aria-label attributes to various interactive elements within the ChatView component, including the avatar toggle, mute/unmute agent voice, voice input (mic), send button, and message input textarea, to enhance screen reader compatibility.
  • Button Type Specification: Explicitly set type="button" for all buttons to prevent unintended form submissions, improving form behavior and accessibility.
  • SVG Accessibility: Applied aria-hidden="true" to SVG icons embedded within buttons, ensuring that decorative images are ignored by assistive technologies and do not create redundant announcements.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • apps/app/src/components/ChatView.tsx
    • Added type="button" to several buttons to prevent accidental form submissions.
    • Introduced dynamic aria-label attributes for the avatar toggle, mute/unmute voice, and voice input buttons.
    • Added a static aria-label="Message input" to the chat textarea.
    • Implemented aria-label for the send message button, dynamically changing based on its state.
    • Set aria-hidden="true" on SVG elements within buttons to improve screen reader experience.
Activity
  • PR created automatically by Jules for task 5106433068055661388, initiated by @Dexploarer.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request significantly improves the accessibility of the ChatView component by adding necessary ARIA attributes and ensuring buttons have the correct type. The changes are well-implemented and follow accessibility best practices. I have one minor suggestion to enhance consistency across the component's buttons by adding a title attribute to the 'Send' button, which will provide a helpful tooltip for mouse users.

Comment on lines 434 to 442
<button
type="button"
className="h-[38px] px-6 py-2 border border-accent bg-accent text-accent-fg text-sm cursor-pointer hover:bg-accent-hover disabled:opacity-40 disabled:cursor-not-allowed self-end"
onClick={handleChatSend}
disabled={chatSending}
aria-label={chatSending ? "Sending message" : "Send message"}
>
{chatSending ? "..." : "Send"}
</button>

Choose a reason for hiding this comment

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

medium

For consistency with other buttons in this component that use the title attribute to provide a tooltip, I suggest adding one to the 'Send' button as well. This will improve the user experience for mouse users.

          <button
            type="button"
            className="h-[38px] px-6 py-2 border border-accent bg-accent text-accent-fg text-sm cursor-pointer hover:bg-accent-hover disabled:opacity-40 disabled:cursor-not-allowed self-end"
            onClick={handleChatSend}
            disabled={chatSending}
            title={chatSending ? "Sending message" : "Send message"}
            aria-label={chatSending ? "Sending message" : "Send message"}
          >
            {chatSending ? "..." : "Send"}
          </button>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant