Skip to content

🎨 Palette: Add accessible auto-scrolling to chat timeline - #193

Open
MEKXH wants to merge 1 commit into
devfrom
palette/chat-timeline-a11y-autoscroll-11453457541069200238
Open

🎨 Palette: Add accessible auto-scrolling to chat timeline#193
MEKXH wants to merge 1 commit into
devfrom
palette/chat-timeline-a11y-autoscroll-11453457541069200238

Conversation

@MEKXH

@MEKXH MEKXH commented May 31, 2026

Copy link
Copy Markdown
Owner

πŸ’‘ What: Added accessible auto-scrolling to the ChatTimeline component in the web UI.

🎯 Why: Users in chat interfaces expect the view to automatically follow the newest messages, especially when waiting for AI responses. Additionally, screen readers need explicit ARIA hints to announce live updates smoothly.

πŸ“Έ Before/After:
Before: Users had to manually scroll down to read the full output of long AI responses, and screen readers did not know the container was a live updating chat log.
After: The interface automatically pins to the bottom as new messages stream in or states change, and screen readers gracefully announce updates.

β™Ώ Accessibility:

  • Added role="log" to semantically define the area.
  • Added aria-live="polite" to gently announce incoming updates.
  • Bound aria-busy to the isSending state so screen readers know when the system is actively waiting/processing.

PR created automatically by Jules for task 11453457541069200238 started by @MEKXH

This commit adds a micro-UX improvement to the `ChatTimeline` component
by implementing a screen-reader friendly auto-scroll mechanism.

1. Binds a template ref to the scrollable container.
2. Applies `role="log"` and `aria-live="polite"` so screen readers are
   aware of updates.
3. Conditionally applies `aria-busy` based on the `isSending` state.
4. Uses a Vue `watch` with `{ flush: 'post' }` to safely read `scrollHeight`
   after the DOM patches and automatically scroll to the bottom.

Co-authored-by: MEKXH <59291264+MEKXH@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