Plasma Accessibility: Kickoff Application starter and Focus handling
Howdy Plasma List, My name is chrys and I m very new here. I currently started with Frederik (my mentor) some work on Plasma Accessibility. We try to bring an Accessibility team back on rail and try improve the situation here. We already make some progress here and continue our work in that area. First of all, thanks for those an wonderful desktop environment. Our first goal is to make next plasma release initial "useful" for bind people. that means we want to be able to do basic tasks. 1. be able to use the desktop 2. Launch an application 3. Switch between applications and windows. point 1. and 3. are already done :) yay! I currently work to make the default application launcher "kickoff" accessible. I already have an local patch floating around to add the missing A11y Name/ Role to the entries. While i did my tests I recognized that the focus handling of that the focus handling of Kickoff is completely broken. In fact the highlighted area what represents the current selected item is just an colorful overlay (some kind of fake focus), but the real focus is always set to the search field. The problem is that screen readers need to know what widget or item currently has the focus to present it properly. if the focus never changes, like in this case it never go away from the search entry, the screen reader does not see the fake focus. so it never knows that you change the item. I have 3 efforts here: 1. i want to sensitize that proper focus handling is important, because i see this behave in other areas too (i.e. clipboard manager plasmoid in panel) and want to start an discussion how to avoid this behave in futur since it is just wrong... 2. i tried to fix the kickoff focus issue. but i failed badly. is there someone out there, with deeper knowledge of kickoffs structure, who can help me out fixing the keyboard and focus handling? 3. we should also consider checking the other widgets and fix those if needed. I currently evaluate what else is affected by this issue. what do you think? for questions or feedback just let me know. so greetings from your new Accessibility Team :) chrys
Re: Plasma Accessibility: Kickoff Application starter and Focus handling
Howdy Edmundson, Oh really? This is incredible awesome. Its the last pice of puzzle what would fit our goal - make most important Desktop components accessible and make plasma initial (very basic) usefully for blind people. Would be very exciting if you could bring your patch in place. I recognize some similar work in this area. To avoid duplicate work and be able to fix the complete issue maybe you can take a look at this (maybe it could unified with your patch or something): D16988: https://mail.kde.org/pipermail/plasma-devel/2018-November/090642.html Cheers chrys On søndag 18. november 2018 18:08:27 CET David Edmundson wrote: > I started a patch a while ago in a branch: > D7780: Make Kickoff expose items to accessibility > > Which rewrote a lot as the focus handling was all over the place. > > However, in the meantime there was another big patch to kickoff that meant > I needed to resolve all the merge conflicts in mine, and I kept putting it > off - and it hasn't been merged yet. > I should get on with it. Wow, that would be totally awesome :) We have quite > a bunch of other tasks, but priority wise this is super important for > accessibility. Thanks a lot for taking care of this. Cheers, Frederik > > David
Make Kicker accessible
Howdy David, i wonder if we can revoke the following for the next version of plasma? https://phabricator.kde.org/D7780 would be very awsome to not have it stalled if you already did most of the work and have an accessible default menu :). cheers chrys
Accessibility in Plasmas new notification system
Howdy Joanie, I just give an talk to kbroulik ( the creator of Plasmas new awsome notification system). see here: https://blog.broulik.de/2019/05/next-generation-plasma-notifications/ He told me that accessibility is not yet implemented. But I see notifications are an very importaint part of an desktop system. Problem for make it accessible is, that it currently doesnt get the focus at any time. Is there a best practice to implement this? how does gnome do this? how is orca awaiting for incomming notifications? do you know how we can make this happen? Sorry for bother you with so basic stuff but you are the only one person I know what can answer those issues properly. maybe a nice side notice for you (and others). We currently work on an accessibility HIG for KDE. https://hig.kde.org/accessibility/index.html Still a WIP, but if someone wants to add some good content just contact me. It should contain: - Keyboard navigation - Focus handling - Set A11y Lables/ Descriptions/ roles - howto test for good a11y cheers chrys
Re: [orca-list] Accessibility in Plasmas new notification system
Howdy Joanie, oh this is pritty awsome! thanks for this information. I will forward it to plasma-devel and kbroulik. fore sure they will like your answer! mercy, cheers chrys Zitat von Joanmarie Diggs : Hey Chrys. Regarding notifications, it should be pretty simple: 1. Give it ROLE_NOTIFICATION 2. Be sure it emits an object:state-changed:showing event 3. Be sure the displayed text is exposed via the accessible text interface, either on the notification itself or in the accessible children of the notification In theory, that should do it. Orca's looking for notifications that announce their appearance because, like you stated, they don't get focus. Hope this helps. BTW, I'm not subscribed to plasma-devel, so I'm not sure if my CCing them will be sufficient. If it's not, and if they need what I've stated above, please forward it to them. Thanks again for all your work on this! --joanie On 6/6/19 7:45 AM, ch...@linux-a11y.org wrote: Howdy Joanie, I just give an talk to kbroulik ( the creator of Plasmas new awsome notification system). see here: https://blog.broulik.de/2019/05/next-generation-plasma-notifications/ He told me that accessibility is not yet implemented. But I see notifications are an very importaint part of an desktop system. Problem for make it accessible is, that it currently doesnt get the focus at any time. Is there a best practice to implement this? how does gnome do this? how is orca awaiting for incomming notifications? do you know how we can make this happen? Sorry for bother you with so basic stuff but you are the only one person I know what can answer those issues properly. maybe a nice side notice for you (and others). We currently work on an accessibility HIG for KDE. https://hig.kde.org/accessibility/index.html Still a WIP, but if someone wants to add some good content just contact me. It should contain: - Keyboard navigation - Focus handling - Set A11y Lables/ Descriptions/ roles - howto test for good a11y cheers chrys ___ orca-list mailing list orca-l...@gnome.org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
