Issue Bug Under Review

#111451Form editor stage: nested interactive controls and no edit button

Josua Vogel 11/14/26, 17:17 updated 11/20/26, 13:36

Description

Problem

Every form element on the form editor stage is rendered as a focusable box with role="button" and an aria-label. The box contains the element toolbar with its own buttons (“Create new element before/after”, “Remove”). An axe scan of the stage reports the WCAG violation nested-interactive (serious) for every element: a control with the button role must not contain focusable descendants, and screen readers may not announce the inner buttons.

The stage also handles Enter and Space for any descendant of the box. A keyboard user who focuses “Remove” or “Create new element after” and presses Enter only selects the element; the button action is never triggered.

The toolbar has no explicit “Edit” control. Opening an element in the inspector is only possible by clicking anywhere on the box, which is not discoverable. The mouse cursor signals clickability only through the drag-and-drop handle class, so it depends on sortability rather than on the click action.

Steps to reproduce

  1. Open Web > Forms and edit a form that contains at least one element, e.g. a Text field.
  2. Run an axe accessibility scan (WCAG 2.1 A/AA) on the stage area: nested-interactive is reported for each stage element.
  3. Press Tab until the “Remove” button of an element toolbar has focus, then press Enter: the element gets selected, but the remove confirmation does not open.
  4. Look for an explicit control that opens the element in the inspector: there is none.

Reviews 2

History 05