Skip to content

🎨 Palette: Accessibility improvements for form and dropzone#62

Draft
Nawayisus wants to merge 1 commit intomainfrom
palette/a11y-dropzone-and-labels-13867297142629796389
Draft

🎨 Palette: Accessibility improvements for form and dropzone#62
Nawayisus wants to merge 1 commit intomainfrom
palette/a11y-dropzone-and-labels-13867297142629796389

Conversation

@Nawayisus
Copy link
Copy Markdown
Owner

💡 What: Added for attributes to form labels, improved keyboard and screen reader accessibility for the file upload drop zone, and added dynamic ARIA properties to the progress bar.
🎯 Why: To make the application fully navigable via keyboard, ensure screen readers can announce dynamic status changes, and follow standard web accessibility practices without changing core functionality or layout.
Accessibility:

  • Linked labels to inputs (for="...")
  • Added tabindex="0", role="button", aria-label to drop zone
  • Added keyboard 'Enter/Space' triggers for the file input
  • Visual focus mapping to existing highlight functions
  • Added aria-live="polite" for dynamic status text
  • Added dynamic aria-valuenow updates to the progress bar

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

Added `for` attributes to form labels in `index.php` linking them to their corresponding `id`s.

Enhanced the file upload `#dropZone` to be fully accessible by adding `tabindex="0"`, `role="button"`, and appropriate ARIA labels. Added JavaScript logic to map keyboard focus/blur events to the visual highlight states. Furthermore, enabled users to trigger the file selector using the 'Enter' or 'Space' keys, while preventing event bubbling that could cause double-dialog issues. Finally, added `aria-live="polite"` to status messages and a dynamic `aria-valuenow` attribute to the progress bar for proper screen reader communication.

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