🎨 Palette: Make "Coming soon" buttons discoverable for screen readers #37
Conversation
Replaces the native `disabled` attribute with `aria-disabled="true"` and event prevention for "Coming soon" buttons in the Compose interface. This ensures these buttons remain in the keyboard tab order, allowing screen reader users to discover these future features instead of them being completely invisible. The visual styling remains identical.
|
👋 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 For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This PR improves the accessibility of the "Coming soon" placeholder buttons in the Compose interface.
Changes:
disabledattribute witharia-disabled="true"on formatting tool buttons (Attach, Link, Emoji, Photo) and "More options".onClick={(e) => e.preventDefault()}to prevent action while allowing focus.cursor-not-allowed, gray colors).Why:
Native
disabledbuttons are removed from the document's tab order. This means keyboard-only and screen reader users would skip these elements entirely, missing the "Coming soon" context that sighted users receive via tooltips and visual cues. This change makes the interface more inclusive by ensuring all users can discover these planned features.PR created automatically by Jules for task 6252114840815814953 started by @Mr-Dark-debug