Conversation
Added aria-busy attributes to buttons that enter a loading state during async operations (exporting, syncing, refreshing) to correctly alert screen readers of the busy state. Co-authored-by: aarjava <218419324+aarjava@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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Added aria-busy attributes to buttons that enter a loading state during async operations (exporting, syncing, refreshing) to correctly alert screen readers of the busy state. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
1 participant
💡 What: Added
aria-busyattributes to buttons when they enter a loading state.🎯 Why: When a background process (like syncing or exporting) is actively running, screen readers need to be alerted that the element is busy. Currently, visual indicators (like the
Loader2spinner) were present, but assistive technologies were not properly notified.📸 Before/After: Visual changes are non-existent, this strictly affects the DOM (
aria-busy="true").♿ Accessibility: Ensures that screen readers know the button is actively busy processing a request.
PR created automatically by Jules for task 4546417163686814912 started by @aarjava