Issue Bug Closed

#110569Enable Keyboard-Accessible Page Moving in the Page Tree

Jennifer Geiß 08/31/26, 07:59 updated 10/19/26, 11:45

Description

Affected versions

TYPO3: 13.4.32
GSB: 11.2.2.212

Description

The page tree in the TYPO3 backend can be reached and navigated using the keyboard and arrow keys. However, moving a page cannot be completed entirely without using a mouse.
The currently available drag-and-drop functionality requires a pointing device. The “Cut” and “Paste” actions available in the context menu provide an alternative in principle. However, in Safari on macOS without VoiceOver enabled, the context menu cannot be opened using the keyboard.
There is currently no other fully keyboard-accessible way to move a page.

Steps to reproduce

  1. Log in to the TYPO3 backend.
  2. Open the “Page” module.
  3. Focus the page tree using the keyboard only.
  4. Navigate to a designated test page using the arrow keys.
  5. Try to move the page without using a mouse.
  6. Try to open the context menu using the keyboard only.
  7. Try to execute the “Cut”, “Paste after”, and “Paste into” actions.

Actual result

A page can only be moved using one of the following methods:
  • Drag-and-drop with a mouse or another pointing device.
  • A context menu opened with a mouse or through a screen reader.
  • Without a mouse and without a screen reader, the complete page-moving operation cannot be performed.

Expected result

Moving a page must be possible entirely through a standard keyboard interface.
For example:
The context menu could be made focusable and operable using the keyboard, or
another fully keyboard-accessible page-moving function could be provided.
The chosen solution must allow users to cut a page, select the target position, and paste the page there using the keyboard only.

Acceptance criteria

  • A page entry in the page tree can be focused and selected using the keyboard.
  • The available actions for a page entry can be opened without a mouse or screen reader.
  • The “Cut” action is reachable and executable using the keyboard.
  • The “Paste after” and “Paste into” actions are reachable and executable using the keyboard.
  • The complete page-moving operation can be completed without a pointing device or screen reader.
  • Keyboard focus remains visible and traceable throughout the entire operation.
  • The selected target position or paste position is clearly identifiable.
  • After completing the operation, the page is located at the selected position.
  • The functionality is tested at least in Safari on macOS without VoiceOver.
  • Existing keyboard and arrow-key navigation within the page tree continues to work.
  • No new keyboard, focus, or operability issues are introduced.

Standards reference

  • BITV test step 9.2.1.1, “Usable without a mouse”
  • WCAG 2.1 Success Criterion 2.1.1, “Keyboard” – Level A
    All functionality must be operable through a keyboard interface unless the underlying function requires input that depends on the path of the user’s movement.
  • EN 301 549, section 9.2.1.1
    Keyboard access.

Reviews 0

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

History 4

  1. Markus Timtner commented and changed Complexity trivial Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-10-19T10:04:10+00:00" > 10/19/26, 10:04 </span>

    With the Shortcut “Shift+F10” the context menu of the page tree can be opened.

    There, you can select “Cut” or “Copy”, move the cursor in the page tree to the desired location, and then paste via the context menu again.

    So, it seems not to be an issue – can be closed.

  2. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-19T10:52:36+00:00" > 10/19/26, 10:52 </span>

    closed as requested. if still valid, please contact me on slack best to reopen or provide a new issue if this is still valid for v14

  3. Sebastian Jansen commented <span data-processor="relativetime" data-value="2026-10-19T11:23:28+00:00" > 10/19/26, 11:23 </span>

    @just2b Hi, I just tested this on my MacBook using Chrome. I can’t open the context menu with Shift+F10. Keyboard navigation in the page tree works fine, but the shortcut does nothing. Can anyone reproduce this on macOS?

  4. Markus Timtner commented <span data-processor="relativetime" data-value="2026-10-19T11:45:05+00:00" > 10/19/26, 11:45 </span>

    on macOS, the default shortcut for context menus is “Fn+Shift+F10”