Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-15873

Source: Content does not update for screen reader users

    Issue Summary

    On the "Source" page, the content of the selected tab is not available for screen reader users.

    Note: This issue has also observed on following pages

    • Branches
    • Commits

    Steps to Reproduce

    1. Open the "Source" page.
    2. Turn on the screen reader, navigate to the "tags" tab and activate it.
    3. Observe that the content from the previous tab, that is "branches" is available for screen reader users instead of the selected tab.

    Screenshot 1

    Screen Recording

    Screen Recording 2023-10-04 at 3.15.42 PM.mov

    Actual Results

    When the user activates the "tags" tab, the screen reader focus goes to the content of the "branches" tab.

    As a result, it will create confusion in the minds of screen reader users regarding the selected tab.

    Expected Results

    When a particular tab is selected, the content of the selected tab should be available for screen reader users. Make sure that the content of the other tabs is hidden unless it is selected. Use the "aria hidden" attribute to the content of the other tabs when the selected tab gets focus.

    Workaround

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

    Environment

    MacBook Pro (14-inch, 2021)
    macOs Ventura  13.4
    Chrome - Version 114.0.5735.106 (Official Build) (arm64)
    Firefox- Version 112.0. 1
    Safari- Version 16.5 (18615.2.9.11.4)
    JAWS- Version 2023
    NVDA- Version 2023
    Voiceover - Version Latest

        Form Name

          [BSERV-15873] Source: Content does not update for screen reader users

          There are no comments yet on this issue.

            Unassigned Unassigned
            2ed0908a25bc Tanmay Mirgal (Inactive)
            Affected customers:
            0 This affects my team
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: