Cards Macro: Card creation is inaccessible for screen reader and keyboard-only users

XMLWordPrintable

    • Severity 3 - Minor
    • Accessibility

      Issue Summary

      The card creation functionality is not conveyed programmatically to screen readers and cannot be accessed using a keyboard.

      Test Environment 

      Cards

      Steps to Reproduce

      1. Open the Confluence Cloud instance.
      2. In the sidebar navigation, navigate to and expand the “Spaces” button, then open any space.
      3. In the header section, navigate to and expand the “Create” button, then activate the “Page” link.
      4. In the editor, type “/cards” to insert the Cards macro.
      5. Using a screen reader and keyboard, press Alt+F10 on Windows or Option+F9 on Mac to navigate to the Cards macro’s floating toolbar and activate the Edit control.
      6. Attempt to add a Label, Title, and Description, and interact with the associated card functionalities.
      7. Observe that the card creation functionality is not conveyed programmatically to screen readers and cannot be accessed using a keyboard.

      Screen Recording

      Cards Macro Issue.mp4

      Actual Results

      When the user types “/cards” and inserts the Cards macro in the editor, a set of cards is added. However, when screen reader users navigate within the editor using the arrow keys, the information within the cards is not conveyed to them.

      The screen reader reads the region as blank.

      Additionally, when the user presses Alt+F10 on Windows or Option+F9 on Mac to navigate to the Cards macro’s floating toolbar and activates the Edit control to modify a card, the following issues are observed while interacting with the Cards macro using a screen reader and keyboard:

      • The Label, Title, and Description fields are unlabelled.
      • The role information for the Label, Title, and Description fields is not conveyed programmatically to screen reader users.
      • Users are unable to navigate to the Label, Title, and Description fields using a keyboard.
      • Users are unable to upload their desired image using a screen reader or keyboard.
      • Users are unable to remove cards as needed.
      • The overall card creation and editing functionality is inaccessible to screen reader and keyboard-only users.

      As a result, screen reader and keyboard-only users are unable to create cards using the Cards macro.

      Expected Results

      The card creation functionality should be fully accessible to both screen reader and keyboard-only users.

      Apply the following changes:

      • The presence and information of each card should be conveyed programmatically to screen readers.
      • When the user presses Alt+F10 on Windows or Option+F9 on Mac to navigate to the Cards macro’s floating toolbar and activates the Edit control, focus should move to the card widget.
      • A descriptive label should be provided for the Label, Title, and Description fields.
      • The role information of the Label, Title, and Description fields should be conveyed programmatically to screen reader users.
      • All fields should be operable and accessible using a keyboard.
      • Users should be able to remove cards as needed.
      • The upload image or choose image/icon functionality should be accessible to both screen reader and keyboard-only users.
      • The overall card creation and editing process should be fully accessible to screen reader and keyboard-only users.

       

      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 Sequoia 15.7.1
      Operations - Windows11
      Chrome - Version 142.0.7444.135 (Official Build) (64-bit)
      Safari- Version 26.0.1
      JAWS- Version 2023
      NVDA- Version 2025.3
      VoiceOver - Version Latest

            Assignee:
            Unassigned
            Reporter:
            Chirag Goyal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: