System dashboard : ARAI role used incorrectly for Actions menu.

XMLWordPrintable

    Issue Summary

    On system dashboard page, the ARIA role="menu" is provided incorrectly to the <div> element of the popup which appears when user activates "Actions (...)" link inside "Assigned to me" table.

    Similar issue found on following page

    • Kanban board 
    • Issue search.

    Bug Ref: 734910

    Steps to Reproduce

    1. Navigate to the system dashboard page.
    2. Navigate to the "Action (...)" link inside "Assigned to me" table & activate it.
    3. Inspect the code of menu popup.
    4. Observe that the role="menu" is provided to the <div> element incorrectly.

    Actual Results

    The ARIA role="menu" is provided incorrectly to the <div> element of the popup which appears when user activates "Actions (...)" link inside "Assigned to me" table.

    The menuitem elements are not direct children of the menu element. Also multiple unordered lists are used inside the menu popup incorrectly.

    Also the code of menu popup is present at the end of the page incorrectly. 

    This makes screen reader users difficult to access the menu effectively.

    Expected Results

    Ensure following fixes are implemented.

    • All the menuitems should be marked inside single <ul> element & other <ul> elements should be removed.
    • The role="menu" attribute should be removed from <div> element & should be provided to the <ul> element.
    • Provide role="presentation" or role="none" attribute to all the <li> elements inside menu popup.
    • The code of menu popup should be present right after the code of menu button.

    Refer to the following menu button example from W3C authoring practices.

    https://www.w3.org/TR/wai-aria-practices-1.1/examples/menu-button/menu-button-links.html 

    Screenshot

    System dashboard

    Kanban Board

    Issue search - Export menu

    Issue search - Filter Actions Menu

    Issue search - Tools menu

    Workaround

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

      1. Screenshot 2022-03-15 at 5.39.14 PM.png
        865 kB
        ssuryavanshi
      2. Screenshot 2022-03-15 at 5.42.35 PM.png
        991 kB
        ssuryavanshi
      3. Screenshot 2022-03-15 at 6.16.55 PM.png
        1.03 MB
        ssuryavanshi
      4. Screenshot 2022-03-15 at 6.18.49 PM.png
        958 kB
        ssuryavanshi
      5. Screenshot 2022-03-15 at 6.23.20 PM.png
        900 kB
        ssuryavanshi
      6. Screenshot 2025-01-20 at 5.59.38 PM.png
        807 kB
        Saiman Khan

          Assignee:
          Unassigned
          Reporter:
          Matthew Brennan
          Votes:
          1 Vote for this issue
          Watchers:
          4 Start watching this issue

            Created:
            Updated:
            Resolved: