#91518Keyboard usage in the TYPO3 backend
Description
This epic collects all issues related to keyboard usage in the backend.
When improving the keyboard interactivity, accessibility of the usage and patterns should be considered, too.
Frontend tests for the keyboard interactivity improvements need to be added to ensure they keep working.
The goal is to get the backend WCAG compatible. Keyboard interactivity not only improves accessibility, but also the usability for every user.
All fixes need to compatible with all browsers supported by TYPO3 and work with common screen readers.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[TASK] Keyboard usage in the TYPO3 backend Resolves: #91518 Releases: main
Subtasks 1
Related issues 15
- Bug #76228Keyboard accessibility of TCA type select
- Bug #81478Datepicker in backend - unlogical behaviour with keyboard navigation
- Feature #89496Make context menu usable via keyboard
- Feature #89590Add an option to jump to specific areas in the backend
- Epic #89595Improve accessibility of backend
- Bug #91645Incorrect keyboard focus order in tab menus
- Bug #92680Dropzone of file upload is not usable by keyboard
- Bug #92681Buttons in IRRE headers do not behave like buttons
- Bug #92682IRRE inline elements cannot be opened or closed via keyboard
- Bug #92694Buttons in module-docheader-bar do not behave like buttons
- Bug #92695Search modal dialog cannot be used with a keyboard
- Bug #92696Not all elements displayed as button behave like buttons
- Feature #97347Allow keyboard navigation in live search
- Bug #104171Make context menu fire 'click' on keyboard spacebar press
- Bug #104530Keyboard usage in Module Menu: use of ENTER/SPACE not consistent