| Summary: | Kirigami.GlobalDrawer is not keyboard navigable out of the box | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kirigami | Reporter: | Thiago Sueto <herzenschein> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | nate, notmart |
| Priority: | NOR | Keywords: | accessibility |
| Version First Reported In: | 6.14.0 | ||
| Target Milestone: | Not decided | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
I do agree. But, i'm not sure what the default shortcut should be? (and how an app can customize it at that point) (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 |
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