There is already a (duplicate) bug for ocular to add caret navigation
https://bugs.kde.org/show_bug.cgi?id=186794
https://bugs.kde.org/show_bug.cgi?id=392700

In T10059#167742, @apol wrote:

This should be improved for other UXs. For example at the moment it can't be used with touch either because buttons appear on hover.

I see there is already some effort. Maybe it broke somehow. Orca is not able to speak the terminal window.
https://github.com/KDE/konsole/blob/master/src/TerminalDisplayAccessible.cpp

Not sure, maybe this is the initial idea here but:
I wonder if it would be a good idea to have this high contrast cursor theme with the complement colors of the background?
this its how its done in other operating systems and would be the best way to have it always high in contrast for guys with people problems as well.

Currently awsome progress is happening by @rooty and @davidedmundson, so I set it to WIP

I splitted this into 2 different more concrete tasks

Yay it landed! :) *congrats* and thanks for your hard work here.
is this closed then?

so this could be closed?

krunner seems to work just fine in first place.
I close this for now since it seems to be an relic of the past.

In T7033#165384, @gladhorn wrote:

@davidedmundson do you have plans about this? @chempfling did you play with the network settings? Is there even any way to open the plasmoid at this point in time? I'll put this back to todo for now.

this is blocked by T10065

while create more atomic tasks this one is invalid now and replaced by T10065

In D16988#362160, @rooty wrote:

Okay so from what I can tell:

(1) Kicker takes the focus off the search field when you go through the results by either mouse or keyboard. This makes it easy to go back to the search field by typing or using the arrow keys (to add more words etc.)
(2) Krunner becomes unfocused if you use the arrow keys, but not if you hover over the search results with your mouse, and it's still possible in either case to append your search same as in Kickoff.
(3) Kickoff (the old, the master and this patch) seems to leave the search field focused at all times while you go through the results, and it's possible to add more characters to the search like in (1) and (2).
(4) Clipboard behaves pretty much like this patch except pressing the Esc key doesn't make it unfocused again.

Any thoughts on how to reconcile all these differences? It might take some doing 😅

started an mailing thread in plasma-devel

Is this still an issue?
can you explain what the issue here is?
just for clearification and to make me understand how needed this is and what it does?

Another idea, what about imagine the desktop as a "big window" and "just" make Tab (focus next control) or ctrl + Tab (focus next panel) chain working here. just like in an normal window.
Would be natural (and consistent) as well and you could just use tab to cycle the plasmoids.

Gnome has the Accessibility Switcher for this (CTRL + ALT + TAB) it toggles between the Panels and the Desktop Area.

works and locks very good to me.

In D16383#360191, @hein wrote:

@chempfling Do you need help pushing this?

We’re currently missing an opportunity to develop a relationship with a11y, a group that already has strong relations with the Linux
Foundation and GNOME.

Ah now i know why i thought the keyboard nav doesnt work.
It seems that you cannot tab out of some categorys (for example "notification"). if you tabbed in once you cannot go out with arrow or shift + tab.

In T7034#166345, @gladhorn wrote:

OK, I seem to have reached something surprisingly simple: D16638 and D16664 give me a tab box that works with Orca.
The requestActivate is needed to get the focus into the window, the window manager hint has to go (are there side-effects?) and after that pressing alt-tab announces a window containing labels for all other windows. The role should be adjusted, but compared to everything else that should be rather trivial.

In T7038#164740, @chempfling wrote:

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.

In T7034#165782, @gladhorn wrote:

My plan was not to change anything regarding x11/wayland at all. It can be done purely on the accessibility level - faking it completely.

I figured how to simulate the correct focus behaviour..

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.