You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
UI: Improve accessibility for screenreaders: Not able to delete old conversations #24701
This problem is around for a while now and i always forgot to report it.
As a blind user i can't delete conversations.
The list of conversations is there, though i am not able to open the menu for each conversation.
How do i open those menus or how does the new concept work?
Tested with llama.cpp b9670 and NVDA 2026.1.1 on Windows 11 and Firefox 151.0.4 though other screen readers should show the same issue.
As far as i know there is a possibility to show elements to screen readers that other users can't see.
But i'll let the GUI people decide what to do. 👍😉
@domasofan I've looked at the code. The actions dropdown (Delete, Edit, etc.) only renders in the DOM on mouse hover ({#if renderActionsDropdown}), so screen readers never see it. I can fix this by always rendering the dropdown but keeping it visually hidden until hover/focus. Would this approach work?
forgot to add as a screen reader user, you can't do mouse overs. at least not reliably.
So if there are more mouse overs in the UI it would be great to also have a look at them too.
@domasofan
I investigated the code in SidebarNavigationConversationItem.svelte
The root cause - two problems:
the actions dropdown (Delete, Edit, etc.) is conditionally removed from the DOM via {#if renderActionsDropdown}, so screen readers never see it
the outer element is a with nested interactive elements inside (links, buttons) which is invalid HTML
what fix i have done :
replaced the outer
with a
+ an absolute overlay button for selection
always render the dropdown in the DOM, use CSS opacity to hide/show it (which is already partially there bcz opacity is 0)
added :focus-within alongside every :hover rule so keyboard navigation works
I also found 2 other components missing group-focus-within:opacity-100 alongside group-hover:opacity-100:
Activity
sanjayahari commentedon Jun 17, 2026
@domasofan I've looked at the code. The actions dropdown (Delete, Edit, etc.) only renders in the DOM on mouse hover ({#if renderActionsDropdown}), so screen readers never see it. I can fix this by always rendering the dropdown but keeping it visually hidden until hover/focus. Would this approach work?
domasofan commentedon Jun 17, 2026
Hi,
Yes i guess that should fix the problem.
Greetings and thanks,
Simon
domasofan commentedon Jun 17, 2026
forgot to add as a screen reader user, you can't do mouse overs. at least not reliably.
So if there are more mouse overs in the UI it would be great to also have a look at them too.
sanjayahari commentedon Jun 17, 2026
@domasofan
I investigated the code in SidebarNavigationConversationItem.svelte
The root cause - two problems:
the actions dropdown (Delete, Edit, etc.) is conditionally removed from the DOM via {#if renderActionsDropdown}, so screen readers never see it
the outer element is a with nested interactive elements inside (links, buttons) which is invalid HTML
what fix i have done :
replaced the outer
with aalways render the dropdown in the DOM, use CSS opacity to hide/show it (which is already partially there bcz opacity is 0)
added :focus-within alongside every :hover rule so keyboard navigation works
I also found 2 other components missing group-focus-within:opacity-100 alongside group-hover:opacity-100:
ChatAttachmentsListItemMcpPrompt.svelte
ChatMessageUserPending.svelte
Would you like me to submit a PR for this?
domasofan commentedon Jun 17, 2026
Yes please. that would be very kind of you.
github-actions commentedon Sep 11, 2026
This issue was closed because it has been inactive for 14 days since being marked as stale.