Skip to content

🎨 Palette: Improve Accessibility for Forms and Dropzone#58

Draft
Nawayisus wants to merge 1 commit intomainfrom
palette-accessibility-fixes-17677038160098149687
Draft

🎨 Palette: Improve Accessibility for Forms and Dropzone#58
Nawayisus wants to merge 1 commit intomainfrom
palette-accessibility-fixes-17677038160098149687

Conversation

@Nawayisus
Copy link
Copy Markdown
Owner

💡 What: The UX enhancement added:
Added crucial ARIA and keyboard accessibility attributes to the file dropzone, progress bar, and form labels, as well as the JS handlers to make the dropzone natively actionable via the keyboard.

🎯 Why: The user problem it solves:
The site's main interactive element (the dropzone) was completely unreachable via keyboard navigation, making it difficult to use for users who rely on assistive technologies. Form labels were visually present but programmatically disconnected from their inputs, hurting screen reader usability. The progress bar lacked live announcements.

📸 Before/After: Visual changes:
No visual changes were made, only structural and semantic markup and behavioral JS fixes.

♿ Accessibility: Any a11y improvements made:

  • Dropzone is now fully keyboard focusable and actionable via Space/Enter.
  • Form inputs are correctly labeled for screen readers.
  • Progress bar dynamically announces progress state.

PR created automatically by Jules for task 17677038160098149687 started by @Nawayisus

- Added `for` attributes to Bootstrap form labels linking them to their select elements.
- Made the dropzone keyboard accessible by adding `tabindex`, `role="button"`, `aria-label`, and handling Enter/Space keys (while preventing infinite click loops).
- Updated the progress area to include `aria-live` and dynamic `aria-valuenow` updates.
- Documented dropzone nested interactive element pattern in `.Jules/palette.md`.

Co-authored-by: Nawayisus <154715157+Nawayisus@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.

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