Version: unknown (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.27-11-server Hi, I will be attaching a screenshot of the dialog window in question. it isn't clear at all when should the user hit. what question is the "yes/no" buttons is suppose to answer? a choice drop down + yes/no buttons makes no sense either you give me three choice, or you ask me a simple yes/no question. but not both. unless No is like Cancel but then I'm not sure if the slowkeys already been triggered. this really ain't clear. That said, why is KDE trying to guess if the user has disabilities? because Microsoft Windows(tm) tried to? I will throw a wild guess saying that 99% of KDE user do not have disabilities and that people with disabilities will receive the help of a sysadmin to enable those feature. don't try to figure it out whenever I'm holding a key too long.... in any case, the dialog should be fixed
Created attachment 33008 [details] slow keys confirmation dialog is unintuitive
> don't try to figure it > out whenever I'm holding a key too long.... As a disabled user, we know that this is how to enable accessibility features. Press Shift five times for sticky keys, for instance. As to your 99% figure, you will find that those with manual disabilities can grow to over 5% in some populations, and over 20% for heavy lifelong keyboard users. That said, I do agree that the wording of the dialogue in question should be improved.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
https://phabricator.kde.org/D17533
*** Bug 263575 has been marked as a duplicate of this bug. ***
Patch from Dec 2018 looks reasonable why don't we merge it ?
Because there were outstanding issues raised during the review process, including the use of bold text. Perhaps somebody could take over the work and address outstanding concerns. Would you like to?