Issue Bug Closed

#108990Change Type: Focus lost after changing page type

Christian Jung 02/16/26, 14:46 updated 11/12/26, 17:04

Description

When changing the type in the page properties or in a content element, the form is rebuilt. After closing the informational modal dialog, the keyboard focus jumps to the top of the page instead of staying within the form area. Keyboard users need extra effort to navigate back to the content area.

Steps to Reproduce

  1. Log in to the TYPO3 backend.
  2. Select a page and open the page properties or a content element.
  3. Go to the tab where the Type can be changed.
  4. Change the type to a value that triggers a form update.
  5. Confirm/close the displayed modal info dialog.
  6. Observe: The focus is now at the top of the page, not in the form area anymore.

Impact

  • Keyboard and screen reader users lose context and must perform many extra tab steps to return to the relevant form area.
  • Accessibility is degraded (focus management, predictable interaction).

Definition of Done

  • After changing the type, focus stays within the form context (type or first relevant field).
  • Keyboard-only usage is possible without unnecessary additional navigation.
  • Behavior is consistent across all supported browsers.
  • Manual tests with keyboard-only navigation are performed and documented.

References

  • WCAG 2.1 – 2.4.3 Focus Order
  • WCAG 2.1 – 3.2.2 On Input

Acceptance Criteria

  • After changing the type and closing the dialog, focus is within the form area, not at the top of the page.
  • Users can continue working in the updated form area with the Tab key without long extra navigation.
  • No JavaScript errors or unexpected focus jumps occur.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 2

  1. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-12T17:04:53+00:00" > 11/12/26, 17:04 </span>

    thanks for the creating the issue. currently nothing can be really done here but with #111338 there is a chance to fix that for v15 – hope you understand