mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1702] Add profile: radio buttons for sync method don't activate with screen readers #1129
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1129
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @domasofan on GitHub (Aug 21, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1702
Which version of floccus are you using?
5.2.5
How many bookmarks do you have, roughly?
6692
Are you using other means to sync bookmarks in parallel to floccus?
No
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Firefox 129.0.1
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
29.0.3
What kind of WebDAV server are you using? (if relevant)
Nextcloud
Describe the Bug
Hello,
Just tried to use Floccus (5.2.5) with a screenreader (NVDA 2024.3) under Windows (10) with Firefox (129.0.1).
It seems that the radio buttons don't get proper focus when activated with the keyboard using a screen reader.
Clicking them with the mouse emulator seems not to work as well.
Greetings,
Simon
Expected Behavior
It should work as expected. :-)
To Reproduce
Try to create a new profile. then try to activate the radio buttons using the keyboard.
Debug log provided
@github-actions[bot] commented on GitHub (Aug 21, 2024):
Hello 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.
I look forward to working with you on this issue
Cheers 💙
@domasofan commented on GitHub (Aug 22, 2024):
Figured out that this problem also exists on my Android phone with Floccus 5.2.5 and Talkback as the screen reader.
@marcelklehr commented on GitHub (Aug 26, 2024):
Hi @domasofan
Thank you for reporting this!
@marcelklehr commented on GitHub (Feb 5, 2025):
I sadly cannot reproduce this in the latest version with Gnome's screenreader on Linux. The inputs seem to have all the necessary aria labels, from what I can see. Can you try again?
@domasofan commented on GitHub (Feb 7, 2025):
Hi @marcelklehr ,
Just tried with v5.4.4.
Radio buttons in creating a profile still don't activate.
Aria is fine though they can't be activated using the keyboard.
Greetings,
Simon
@marcelklehr commented on GitHub (Feb 7, 2025):
Mh, I can reach the radio buttons using the arrow keys.
@domasofan commented on GitHub (Feb 8, 2025):
Hi,
Yes they can be reached.
But can they also be activated?
Greetings,
Simon
@marcelklehr commented on GitHub (Feb 9, 2025):
Yes, with space, I think. Ah, no they activate directly when reaching them via the arrow keys.
@domasofan commented on GitHub (Feb 9, 2025):
Hi,
Thats interesting.
When i try to enable the radio buttons directly that seems not to work.
Though next to the radio button there seems to be a clickable area.
When i use that one the radio buttons above/next to them activate.
@github-actions[bot] commented on GitHub (May 11, 2025):
Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.
Cheers 💙
@domasofan commented on GitHub (May 11, 2025):
Hi,
Still broken.
Greetings,
Simon
@marcelklehr commented on GitHub (May 12, 2025):
I'll try to update the component library used by floccus, but I don't have high hopes for this, especially because I cannot reproduce it.
@domasofan commented on GitHub (May 12, 2025):
👍
I might be able to get a web dev to look it at it as well. Maybe we can find out what is going on.
@github-actions[bot] commented on GitHub (Aug 11, 2025):
Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.
Cheers 💙
@github-actions[bot] commented on GitHub (Aug 17, 2025):
This issue was closed because it has been stalled for 5 days with no activity.