Issue Feature Closed

#108988Clipboard as List instead of Table

Aphisit Chanathale 02/16/26, 08:12 updated 11/06/26, 14:43

Description

Steps to reproduce

Log in to the TYPO3 backend.
Navigate to any module where the clipboard functionality is available (e.g. Page or List module).
Perform actions that populate the clipboard (e.g. copy or cut one or more records/pages).
Open or focus the clipboard panel/area where the entries are listed.
Use a screen reader (e.g. NVDA) to navigate through the clipboard content.

Current result

The clipboard content is rendered as a table structure, which is recognized as a table by the screen reader.
However, the table does not provide any column headers or structural cues that help with understanding the content.
Screen reader users hear a series of table cells without clear information about what each cell means (e.g. which part is the item label, which part is the action).
This makes it difficult for screen reader users to understand and operate the clipboard reliably.

Expected result

The clipboard content is represented using a semantically appropriate structure for a list of items (e.g. one entry per list item) instead of a table.
Screen readers announce the clipboard as a list with a clear number of entries, and each entry is understandable on its own (e.g. “Clipboard item: [label], [actions]”).
Each list item groups all relevant information and controls for a clipboard entry in a logical, linear reading order.
Screen reader users can understand, navigate, and operate clipboard entries with an equivalent level of clarity as sighted users.

Impact

Affects all blind or visually impaired users who rely on screen readers in the TYPO3 backend.
The issue makes it harder to understand what is currently stored in the clipboard and which actions are available, increasing the risk of performing unintended actions.
From an accessibility perspective, this impacts BITV / WCAG 2.1 criterion 1.3.1 (Info and Relationships), because the current table structure does not convey relationships in a useful, perceivable way for this kind of content.

Recommended solution

Replace the table markup used for the clipboard with a list-based structure that better reflects the nature of the content:
Use an ordered or unordered list (
    or
      ) with one entry per list item (
    • ).
      Within each list item, group the information (e.g. item label, type, path) and the available actions (e.g. paste, delete) in a logical reading order.
      Ensure each list item has a clear, accessible label that summarizes the clipboard entry (e.g. using headings, visually hidden text, or ARIA labels when needed).

      Definition of done

      Verify that screen readers announce the clipboard as a list and that each item can be understood and operated independently.
      Keep the visual appearance as close as possible to the original design using CSS, while improving the underlying semantic structure.
      The clipboard is no longer rendered as a table but as a list-based structure (
        /
          with
        1. entries or an equivalent accessible pattern).
          Each clipboard entry is announced by screen readers as a distinct item with all relevant information and controls available in a logical sequence.
          Tested with at least one common screen reader and one major browser to ensure correct announcements and operability.
          No regressions in visual appearance or clipboard functionality (copy/cut/paste and related actions).
          Documentation or developer notes are updated if the DOM structure or components have changed.

          Acceptance criteria

          Clipboard entries are represented using a list structure (
            /
              with
            1. items) instead of a table.
              Each list item contains all relevant information and actions for a clipboard entry in a meaningful reading order.
              When using a screen reader (e.g. NVDA), the clipboard is announced as a list, including the number of items.
              Each clipboard entry is understandable on its own (e.g. item name, type, and actions are clearly conveyed).
              Clipboard functionality (copy, cut, paste, clear, etc.) continues to work without regressions.

Reviews 2

History 710

  1. Maike Kiebele commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-06T09:30:13+00:00" > 11/06/26, 09:30 </span>

    Applied in changeset commit:6a72e4ad1294cf9346ec429d4702664648d44526.