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

      Keyboard and screen reader focus is moving inappropriately while performing the operations such as "Edit", "Write a comment", "Save", "Cancel", etc.

      Steps to Reproduce

      1. Open the "Home page" and navigate to "Pages".
      2. Activate the "Pages" link in left pane.
      3. Access the "Write a comment" text area using TAB key. 

      Screenshot

      Actual Results

      While navigating the "Write a comment" text area, keyboard and screen reader focus is moving to top of the page inappropriately. Similarly while performing the operations such as "Edit", "Reply", etc. As a result, user will have to navigate the entire page content forcefully.

      Expected Results

      Ensure that focus should move logically while accessing the "Write a comment" text area. Ideally focus should move in following order.

      1. Activate "Write a Comment" 
      2. Let User type the comment
      3. User will select one of the options mentioned here: "Preview", "Save" or "Cancel" 
      4. For "Preview": User will check his response and select either "Edit" or "Save"
      5. For "Save": Users response should get displayed.
      6. For "Cancel": Comment text area should get dismissed. 

      Workaround

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

            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

                Keyboard and screen reader focus is moving inappropriately while performing the operations such as "Edit", "Write a comment", "Save", "Cancel", etc.

                Steps to Reproduce

                1. Open the "Home page" and navigate to "Pages".
                2. Activate the "Pages" link in left pane.
                3. Access the "Write a comment" text area using TAB key. 

                Screenshot

                Actual Results

                While navigating the "Write a comment" text area, keyboard and screen reader focus is moving to top of the page inappropriately. Similarly while performing the operations such as "Edit", "Reply", etc. As a result, user will have to navigate the entire page content forcefully.

                Expected Results

                Ensure that focus should move logically while accessing the "Write a comment" text area. Ideally focus should move in following order.

                1. Activate "Write a Comment" 
                2. Let User type the comment
                3. User will select one of the options mentioned here: "Preview", "Save" or "Cancel" 
                4. For "Preview": User will check his response and select either "Edit" or "Save"
                5. For "Save": Users response should get displayed.
                6. For "Cancel": Comment text area should get dismissed. 

                Workaround

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

                        5e496a614b63 Diclehan Erdal
                        c3f9a46dc7c4 Varsha Bansode
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            5e496a614b63 Diclehan Erdal
                            c3f9a46dc7c4 Varsha Bansode
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: