🎨 Palette: [Accessibility] Improve icon-only button screen reader support#234
🎨 Palette: [Accessibility] Improve icon-only button screen reader support#234thirdeyenation wants to merge 1 commit into
Conversation
Co-authored-by: thirdeyenation <133812267+thirdeyenation@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Added explicit
aria-labelattributes to icon-only buttons across the chat navigation, message queue, and task list components. Addedaria-hidden="true"to the inner<span class="material-symbols-outlined">elements.🎯 Why: Without
aria-label, screen readers cannot announce the button's purpose to users. Withoutaria-hidden="true", screen readers will erroneously read out the raw ligature text (e.g., "delete_sweep") instead of the button's intended action, causing confusion for users navigating via keyboard and screen readers.📸 Before/After: Visual presentation remains identical. Semantic HTML improved.
♿ Accessibility: Improves screen reader compatibility for multiple interactive elements by explicitly labeling controls and hiding decorative ligature text from accessibility trees.
PR created automatically by Jules for task 5782302996457941854 started by @thirdeyenation