We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    Issue Summary

    Tabindex attribute defined inappropriately for button

    Note: Similar issue is observed on "Create new page" for "Publish" button. Refer screenshot 2 

               Similar issue is observed on "View inline comments" for "Save" button. Refer screenshot 3   

    Steps to Reproduce

    1. Navigate to "Recent spaces"
    2. Navigate to the "Test" Page.
    3. Navigate to the "comment" section.
    4. Using a screen reader, navigate to the "save" button.

    Screenshot no 1 

    Screenshot no 2

    Screenshot no 3

    Actual Results

    The "Save" button inappropriately uses positive tabindex values. As a result, users of assistive technologies found it challenging to understand the functionality associated with this element.

    Expected Results

    Apply the following changes:

    • Remove tabindex="101" from the <button> element in the page source.

    Since this is the native element we recommend you to remove the tabindex attribute from the <button> element.

    Workaround

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

    Environment

    MacBook Pro (16-inch, 2019)
    macOs Ventura 13.3.1
    Chrome - Version 113.0.5672.63 (Official Build) (x86_64)
    Firefox- Version 92.0 (64-bit)
    Safari- Version 16.4 (18615.1.26.110.1)
    JAWS- Version 2022
    NVDA- Version 2021.2
    Voiceover - Version Latest

          Loading...
          IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

            Issue Summary

            Tabindex attribute defined inappropriately for button

            Note: Similar issue is observed on "Create new page" for "Publish" button. Refer screenshot 2 

                       Similar issue is observed on "View inline comments" for "Save" button. Refer screenshot 3   

            Steps to Reproduce

            1. Navigate to "Recent spaces"
            2. Navigate to the "Test" Page.
            3. Navigate to the "comment" section.
            4. Using a screen reader, navigate to the "save" button.

            Screenshot no 1 

            Screenshot no 2

            Screenshot no 3

            Actual Results

            The "Save" button inappropriately uses positive tabindex values. As a result, users of assistive technologies found it challenging to understand the functionality associated with this element.

            Expected Results

            Apply the following changes:

            • Remove tabindex="101" from the <button> element in the page source.

            Since this is the native element we recommend you to remove the tabindex attribute from the <button> element.

            Workaround

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

            Environment

            MacBook Pro (16-inch, 2019)
            macOs Ventura 13.3.1
            Chrome - Version 113.0.5672.63 (Official Build) (x86_64)
            Firefox- Version 92.0 (64-bit)
            Safari- Version 16.4 (18615.1.26.110.1)
            JAWS- Version 2022
            NVDA- Version 2021.2
            Voiceover - Version Latest

                    mfedoryshyn Maksym Fedoryshyh
                    83061a15f038 Nayan Kamble
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    4 Start watching this issue

                      Created:
                      Updated:
                      Resolved:

                        mfedoryshyn Maksym Fedoryshyh
                        83061a15f038 Nayan Kamble
                        Affected customers:
                        0 This affects my team
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved: