🎨 Palette: Improve accessibility of text-based icons#313
Conversation
Co-authored-by: ralksta <16941050+ralksta@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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
💡 What: Replaced bare text characters (×, ✕, ↗, ↑) acting as icons with accessible screen-reader hidden spans, and added aria-labels to their parent interactive elements.
🎯 Why: Text characters used as icons without proper ARIA attributes are announced confusingly by screen readers (e.g. "times" instead of "Close"). Wrapping them in aria-hidden spans and labeling the buttons makes the UI much more accessible.
📸 Before/After: Visuals remain identical, but screen reader announcements are now descriptive.
♿ Accessibility: Improved keyboard navigation and screen reader support for icon-only buttons across the admin panel and public site.
PR created automatically by Jules for task 17342062838490501257 started by @ralksta