kde-accessibility Digest, Vol 163, Issue 14

[Daniel Crone]

I am totally blind, had used mate and gnome before.
Might k d e be ready for someone like me to try?
Or should I wait?
If it is ready yet, how may I know what keyboard commands to use?
Never have I yet used k d e.
If k d e is ready, how may one download it?

> On Oct 22, 2018, at 6:00 AM, kde-accessibility-request at kde.org wrote:
> 
> Send kde-accessibility mailing list submissions to
> 	kde-accessibility at kde.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mail.kde.org/mailman/listinfo/kde-accessibility
> or, via email, send a message with subject or body 'help' to
> 	kde-accessibility-request at kde.org
> 
> You can reach the person managing the list at
> 	kde-accessibility-owner at kde.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kde-accessibility digest..."
> 
> 
> Today's Topics:
> 
>   1. Status update (chrys at linux-a11y.org)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 22 Oct 2018 12:11:53 +0200
> From: chrys at linux-a11y.org
> To: kde-accessibility at kde.org
> Subject: Status update
> Message-ID:
> 	<20181022121153.Horde.ruMUuPvc-PcaoP4dXobKTA1 at webmail.df.eu>
> Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
> 
> Howdy List,
> 
> as nobody complaind about my idea to be the coordinator or team  
> "leader" of the plasma kde accessibility project, I see me confirmed  
> in this role now.
> 
> Whats current?
> first of all my patch for making desktop icons accessible is applied  
> and backported to 5.12.x, 5.14.x and master.
> https://phabricator.kde.org/D16309
> so YAY!
> 
> I apply for an KDE developer account because i will provide more stuff  
> in near futur.
> https://identity.kde.org/index.php?r=developerApplication/view&id=819
> not sure whats needed here or if i will be confirmed (since i only  
> provide one patch yet). but for sure not my last ;). what brings me to  
> "whats next":
> I started on T9878 "Default application starter menu is missing a11y Labels"
> https://phabricator.kde.org/T9878
> to make our 3 nice preinstalled menus accessible. The ranking of  
> working state:
> 1. "kicker" works best. only issue you cannot navigate to favorite  
> section (for testers i would recomment this!)
> 2. "dashboard" works well. 2 a11y lables are missing. but keyboard  
> navigation doesnt respect the "panel boarders"
> 3. "kickoff" - the default menu. doesnt work at all. only accessible  
> text is the search box.
> I assume this to be fixed to end of the week.
> 
> if anyone is interested in help write code or documentation let me know. :).
> 
> for T7034 "Accessibility in KWin window switcher"
> https://phabricator.kde.org/T7034
> i try to take a look at but its currently to rought for me (whatever  
> on gnome or kde side). so i will ask how this works in gnome on orca  
> list, to get an idea how it works to give an idea how to fix it. on  
> gnome side it looks liek an special stylesheed is set what is  
> interpreted as "ATK_STATE_SELECTED".
> 
> cheers chrys
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility at kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility
> 
> 
> ------------------------------
> 
> End of kde-accessibility Digest, Vol 163, Issue 14
> **************************************************