Epic #91518

Keyboard usage in the TYPO3 backend

Added by Michael Telgkamp about 1 month ago. Updated 29 days ago.

Status:
New
Priority:
Should have
Category:
-
Target version:
Start date:
2020-06-05
Due date:
% Done:

0%

Sprint Focus:

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.


Subtasks

Bug #91592: Modal not closable using ESC when focus is inside elements of iframeNew

Bug #91595: Not all elements displayed as button behave like buttonsNew


Related issues

Related to TYPO3 Core - Bug #76228: Keyboard accessibility of TCA type select New 2016-05-18
Related to TYPO3 Core - Feature #89496: Make context menu usable via keyboard New 2019-10-24
Related to TYPO3 Core - Feature #89590: Add an option to jump to specific areas in the backend New 2019-11-06
Related to TYPO3 Core - Bug #91645: Incorrect keyboard focus order in tab menus New 2020-06-15

History

#1 Updated by Michael Telgkamp about 1 month ago

  • Related to Bug #76228: Keyboard accessibility of TCA type select added

#2 Updated by Michael Telgkamp about 1 month ago

  • Related to Feature #89496: Make context menu usable via keyboard added

#3 Updated by Michael Telgkamp about 1 month ago

  • Related to Feature #89590: Add an option to jump to specific areas in the backend added

#4 Updated by Elisabeth Zeilinger 19 days ago

  • Related to Bug #91645: Incorrect keyboard focus order in tab menus added

Also available in: Atom PDF