#109020Dashboard: focus handling and close button in “Add widget” modal
Description
When the “Add widget” button is triggered via keyboard (Enter), a modal opens, but there is no visible focus right after opening.
When the modal is closed via Esc or other closing actions, focus is not returned to the triggering “Add widget” button.
The close button “x” in the modal has no accessible name and is not clearly announced as “Close” by screen readers.
Expected behavior
- After opening the modal, the keyboard focus is visible and placed on a meaningful first focus target inside the modal.
- When closing the modal, focus is always returned to the triggering “Add widget” button – regardless of how the modal is closed.
- The close button “x” has the accessible name “Close” (e.g. via visually hidden or an ARIA attribute).
Steps to Reproduce
- Open the dashboard in the TYPO3 backend.
- Navigate to the “Add widget” button using Tab.
- Press Enter → modal opens → focus is not visible.
- In the modal, press Esc (or close via “x”, “Cancel”, etc.).
- Focus is not restored to the “Add widget” button afterwards.
Impact
Keyboard users lose orientation because focus is not visible and not handled correctly.
Screen reader users cannot reliably recognize the close button’s purpose.
Violates accessibility requirements (e.g. WCAG 2.1: visible focus, keyboard operability, meaningful focus order).
Definition of Done
- After opening the modal, focus is visible and inside the modal.
- After closing the modal, focus is reliably restored to the “Add widget” button.
- The “x” close button is announced as “Close” by screen readers.
- Behavior has been tested in common browsers and screen readers (at least current Chrome/Firefox/Edge, NVDA/VoiceOver).
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 3
History 2
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:51+00:00" > 04/21/26, 11:23 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-11T21:28:26+00:00" > 11/11/26, 21:28 </span>
I was not able to reproduce that on main. if still valid for you in v14, please let us reopen the issue