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.

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Summary

      When using the Expand macro, the links for each of the collapsed content section are hidden from the keyboard tab order. For those who may not use a mouse to navigate a website or application, using the tab key is essential. When using the tab key the tab focus skips over the Expand links and all the collapsed content is hidden and blocking keyboard-only users and assistive technology users from the content.

      Currently, once the content is expanded the text is readable by a screen reader. But the intention of expandable content is the ability to choose to expand or collapse content. Any collapsed content should be ignored by a screen reader until expanded. A future state for this would be to have each of the expandable links in the keyboard tab order. When a screen reader user focuses on each link, the screen reader should say what state the content is in "expanded" or "collapsed." When the links are activated using the enter key, the screen reader should announce the new state "expanded" or "collapsed." When expanded, and the content appears visually the screen reader user should be able to navigate directly into the newly visible content. The page should not refresh or push the focus to another part of the page. The keyboard focus should remain on the activated link until the person chooses to navigate into the content or elsewhere on the page.

      Steps to Reproduce

      Just use JAWS screen reader or NVDA screen reader.

      Expected Behaviour.

      The focus of the tab key should be able to access the Expanded content

      Actual Behaviour

      When using the tab key the tab focus skips over the Expand links and all the collapsed content is hidden and blocking keyboard-only users and assistive technology users from the content.

            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.

              • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                Summary

                When using the Expand macro, the links for each of the collapsed content section are hidden from the keyboard tab order. For those who may not use a mouse to navigate a website or application, using the tab key is essential. When using the tab key the tab focus skips over the Expand links and all the collapsed content is hidden and blocking keyboard-only users and assistive technology users from the content.

                Currently, once the content is expanded the text is readable by a screen reader. But the intention of expandable content is the ability to choose to expand or collapse content. Any collapsed content should be ignored by a screen reader until expanded. A future state for this would be to have each of the expandable links in the keyboard tab order. When a screen reader user focuses on each link, the screen reader should say what state the content is in "expanded" or "collapsed." When the links are activated using the enter key, the screen reader should announce the new state "expanded" or "collapsed." When expanded, and the content appears visually the screen reader user should be able to navigate directly into the newly visible content. The page should not refresh or push the focus to another part of the page. The keyboard focus should remain on the activated link until the person chooses to navigate into the content or elsewhere on the page.

                Steps to Reproduce

                Just use JAWS screen reader or NVDA screen reader.

                Expected Behaviour.

                The focus of the tab key should be able to access the Expanded content

                Actual Behaviour

                When using the tab key the tab focus skips over the Expand links and all the collapsed content is hidden and blocking keyboard-only users and assistive technology users from the content.

                        Unassigned Unassigned
                        5b643f07cdd7 Gustavo P
                        Votes:
                        4 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            5b643f07cdd7 Gustavo P
                            Votes:
                            4 Vote for this issue
                            Watchers:
                            6 Start watching this issue

                              Created:
                              Updated:
                              Resolved: