Status update

[Frederik Gladhorn]

On mandag 22. oktober 2018 12.11.53 CEST chrys at linux-a11y.org wrote:
> 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.

Congratulations :) I approve!

> 
> 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 ;).

Usually we let people contribute a few patches, to not give rights sfor drive-
by contributors. Once you apply for developer rights, you'll have direct push 
access to all of KDE's repositories.

> 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!)

Nice, that sounds better than I expected.

> 2. "dashboard" works well. 2 a11y lables are missing. but keyboard
> navigation doesnt respect the "panel boarders"

I guess that's fixable... the code is in the same repo as the others I think.

> 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.

Last time I looked this also had massive keyboard issues, if these are fixed, 
then there is actually hope, making the default work is of course always the 
best solution.

> 
> 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".

I think this one is tricky indeed. I'm unsure what Orca expects, for other 
windows, we actually send messages that Windows are active/inactive. If we 
don't give the focus to the window manager, we will need to potentially fake 
this.
We could start a thread on the plasma mailing list at some point, if there is 
no progress.

Cheers,
Frederik


> 
> cheers chrys