In T7034#165364, @gladhorn wrote:

Next to the window switching, there is also desktop switching (virtual desktops) which I consider secondary (but it may be fixed with the same change).

I asked about this to Joanie (the orca maintaier). she was last week on an trip.
https://mail.gnome.org/archives/orca-list/2018-October/msg00270.html
lets wait for her answer.

In T9869#165156, @ngraham wrote:

Congrats! Seems like this should be closed, no?

I currently try to fix ""Application Starter" (default) is missing a11y Labels"
as i figured that the missing labels are the more small problem.

Add Accessibility information to Tabbar in in Dash:
https://phabricator.kde.org/D16383

I wonder why "Row" is used to implement the tab bar at top on the screen in dash menu (instead of the TabBar Widget). everything is custom implemented but i don't see a reason for this?
Maybe it should be considered to replace the custom implementation with the default TabBar/ TabButton classes (what would not require the fix then i think).
the current implementation also loses the focus after switching the tab. but to do this i need more experience with that.

In D16309#347071, @hein wrote:

I'll land it for you (it needs a manual step, which requires a dev account - which you should eventually apply for if you wind up contributing regularly!).

The keyboard navigation for the system settings is completely broken. Focus chain doesnt work. The sidebar often looses the focus magically. This should not only fixed for a11y reasons. This is also a kind of good usability. This effects everyone not just impaired people.

Ok, so nothing to do then. Is this merged automatically once per day or something? Or how do i get the patch into master now? I mark the task as done.

Do i need to do anythin else to get it into master?

ok i hopefully did all right:
https://phabricator.kde.org/D16309

In T9878#164684, @Zren wrote:

• Application Launcher (Kickoff) is the KDE default menu with the tabbed interface.
• Application Menu (Kicker) is the Windows 95 styled menu.
• Application Dashboard (KickerDash) reuses the Kicker source code, but uses DashboardRepresentation.qml as the entry point instead of main.qml. KickerDash's metadata.desktop file is in the kdeplasma-addons repo. Effectively, everything is in the plasma-desktop repo though as that one .desktop file is the only thing outside it.
  
  ----
• https://github.com/KDE/plasma-desktop/tree/master/applets/kickoff/package/contents/ui
• https://github.com/KDE/plasma-desktop/tree/master/applets/kicker/package/contents/ui
• https://github.com/KDE/plasma-desktop/blob/master/applets/kicker/package/contents/ui/DashboardRepresentation.qml
• https://github.com/KDE/kdeplasma-addons/tree/master/applets/kickerdash
• Apps and Docs https://github.com/KDE/plasma-desktop/blob/master/applets/kicker/package/contents/ui/DashboardTabBar.qml#L43

Ah ok, so each „alternative“ when i rigt click on the start button -> alternatives is an own menu? Or do they share the code with just different views?

Since noone is assigned here and i do not know what this issue is going to tell me and my previous poster i close this for now. Keeping the tracker clean :).
If there is a need we can open it anyway with more information.

Ok next i want to polish the default start menu. Its another very importaint component to interact with an desktop.

In T9869#164572, @gladhorn wrote:

Oh wow, this is super awesome! Yay!!!!
The next step is to get your patch in of course. Do you want to put it up for review on phabricator?

i currently try to structure and fix the a11y issues.

Ok i fixed it on my local machine. Orca can now speak the desktop for me.

In T9869#164469, @hein wrote:

Hey! :)

Labels should be done in: plasma-desktop.git:containments/desktop/package/contents/ui/FolderItemDelegate.qml

Additional:
a good startingpoint may be this:
http://doc.qt.io/qt-5/accessible.html#making-applications-accessible
and this
http://doc.qt.io/qt-5/qtquick-quick-accessibility-accessibility-qml.html

awsome that you think about accessibility.

In T9869#164238, @gladhorn wrote:

I don't even see how to keyboard focus the desktop. Do you manage that somehow?

Oh no, i just found the shortcut to focus the destkop. its CTRL + F12 here. Not very intuitive.
anyway CTRL + F12 just brings me to workspace but doesnt focus an icon. this should happen too here. Best would be to focus the last active icon.

hmm now as you say it. i m not able to focus the desktop too. isnt it typical "windows" + d?
i currently cannot really test it because my KDE 5.14 Plasma Shell ignores every shortcut on desktop (also if i mark icons, now arrow, no tab, no ctrl + a, nothing). so maybe it works in theory but its just currently broken until 5.14.1 ( i read its fixed there in this version)

In T9870#164240, @gladhorn wrote:

With kicker you mean the default start menu?

About the additional information: i found the tooltip often shows what is interesting to the user. maybe it can be configurable to append this to the menuentrys. (just an brainstorm)

its not most beautiful ;), but i hope it shows what i think.
I think about to have an shortcut what opens an dialog like in my mockup.
the dialog shows the "plasmoid" structure in an simple tree via submenus.

In T7034#164237, @gladhorn wrote:

I think this is one of the most important tasks for screen reader users. I assume we'll have to contact the KWin developers. Ideally after doing a bit of research how other window managers solve this.

I think it would be awsome to not only focus the panel (because what to do on multible panels and so on) but create an "plasmoid swticher" overall.