Bug 505235 - Kirigami.GlobalDrawer is not keyboard navigable out of the box
Summary: Kirigami.GlobalDrawer is not keyboard navigable out of the box
Status: CONFIRMED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.14.0
Platform: Other Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2025-06-05 13:28 UTC by Thiago Sueto
Modified: 2025-08-31 02:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thiago Sueto 2025-06-05 13:28:36 UTC
Kirigami.GlobalDrawer doesn't have a default shortcut, and it doesn't allow to navigate through its actions via the keyboard.

It is possible to implement a simple shortcut to open the drawer manually with something like this:

```
Shortcut {
    sequences: ["F10"]
    onActivated: globalDrawer.opened ? globalDrawer.close() : globalDrawer.open()
}
```

But:

* it should just be accessible by default
* this opens the drawer even when isMenu: true, and with everything grayed out
Comment 1 Marco Martin 2025-08-26 12:11:33 UTC
I do agree.
But, i'm not sure what the default shortcut should be? (and how an app can customize it at that point)
Comment 2 Thiago Sueto 2025-08-31 02:18:59 UTC
(In reply to Marco Martin from comment #1)
> I do agree.
> But, i'm not sure what the default shortcut should be? (and how an app can
> customize it at that point)

Well, I used F10 because that's the accessible shortcut for opening the main menu or hamburger menu in QtWidgets apps now, as per

https://invent.kde.org/teams/accessibility/collaboration/-/issues/28

and

https://wordsmith.social/felix-ernst/f10-for-accessibility-in-kf6