Scrum Board | Forms: Status message not defined programmetically

XMLWordPrintable

    • Severity 3 - Minor
    • Accessibility

      Issue Summary

      There is no visual or screen reader confirmation upon the addition of any field to the form.

      Steps to Reproduce

      1. Open the Jira Cloud home page.
      2. Select any Scrum project and navigate to Space navigation.
      3. Navigate to the "Forms" tab and activate it.
      4. Select any existing form and open it.
      5. Using a screen reader to navigate to the "Fields" submenu.
      6. Navigate to the desired field you wish to add, and activate the "Add to form" button.
      7. Note that there is no visual confirmation or announcement from the screen reader.
      8. Using the mouse, scroll through the form to verify that the field has been successfully added.

      Screen Recording

      https://www.loom.com/share/6de28474b3b649b28c086f8633a6af81

      Actual Results

      When users add fields such as "Due date", "Fix versions", "Labels", and so on available from the "Fields" submenu by activating the "Add to form" button, there is no visual confirmation or screen reader notification provided on the page. However, the field is successfully appended at the end of the form, which becomes visible upon scrolling down. The same issue occurs when removing fields from the form.

      As a result, screen reader users remain unaware of the fields being added to the form until they have navigated through the entire form to identify these fields.

      Expected Results

      When a field is added or removed, ensure that a visual status message is displayed on the page and is announced by screen readers without shifting the focus.

      Use ARIA live region to make sure that the dynamic update is announced for screen reader users. This can be achieved by either adding a live region role="status" or aria-live="polite" and aria-atomic="true" attributes to the container used to display the message. Make sure the live region is present in the page source by default.

      For more information on implementing the live regions, visit https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions

      Note: This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

      Code Snippet:

      <div role="status" aria-live="polite" aria-atomic="true" class="status-message">
        Field "Due date" added successfully.
      </div> 

      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 26.5
      Windows - 11 pro
      Chrome - Version 148.0.7778.97 (Official Build) (arm64)
      Safari - Version 26.5 (21624.2.5.11.4)
      JAWS - Version 2026
      NVDA - Version 2024.4.2.35031
      Voiceover - Version Latest

              Assignee:
              Pranavi Parasu
              Reporter:
              Anusooya .
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: