Side Navigation: Dual focus indicators and extra tab stop on "More actions" button

XMLWordPrintable

    • Severity 3 - Minor
    • Accessibility

      Issue Summary

      "More actions" menu receives dual focus and requires extra Tab press before focusing menu items.

      Steps to Reproduce

      1. Open the Confluence Cloud homepage.
      2. Open any space and navigate to the Content tree in the side navigation.
      3. Using the "Tab" key, navigate to the "More actions" button for any page item.
      4. Activate the menu using the "Space" or "Enter" key.
      5. Observe that the menu expands, but an additional focus indicator is displayed on the "More actions" trigger button.
      6. Press "Tab" once → the extra focus ring disappears, but focus remains on the trigger and does not move into the expanded menu content.
      7. Press "Tab" a second time → focus finally moves to the first interactive element inside the expanded menu content.

      Screenshot

      Screen Recording

      Screen Recording 2026-09-09 at 2.11.01 PM.mov

      Actual Results

      When the "More actions" button is activated, the menu expands but the trigger button displays dual focus indicators. Pressing “Tab” once removes the secondary focus ring, but focus remains stuck on the container rather than moving into the expanded menu. This occurs because the wrapper <div> enclosing the expanded menu options has tabindex="0".

      As a result, an extra “Tab” press is required to reach the first actionable menu item, creating an unnecessary tab stop for keyboard-only and screen reader users.

      Expected Results

      Ensure keyboard focus follows a logical sequence without redundant tab stops. Only a single, clear focus indicator should be visible on the "More actions" button. Upon activation, focus should move directly to the first actionable menu item without intermediate stops.

      Apply the following changes ->

      • Remove tabindex="0" from the expanded content's container <div> to eliminate the redundant tab stop.
      • Apply role="menu" on the container and role="menuitem" on actionable items with arrow-key navigation support.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

      Environment

      MacBook Pro (16-inch, 2021)
      macOS - Tahoe 26.6.2
      Windows - 11
      Chrome - Version 152.0.7977.77 (Official Build) (arm64)
      Edge - Version 152.0.4191.66 (Official Build) (64-bit)
      Safari - Version 26.2 (21623.1.14.11.9)
      JAWS - Version 2026
      NVDA - Version 2026.1.1
      VoiceOver - Latest version

              Assignee:
              Nick Bourlier
              Reporter:
              Anusooya . (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: