Summary

      Skip navigation links exist, but the targets for the links either do not exist or the links are not keyboard accessible.

      An in-page link contains the words "skip" or "jump" and is hidden with CSS display:none or visibility:hidden, or the link has an href attribute that does not match the id value of another element within the page or the name attribute value of an anchor element within the page.

      Broken links on the main dashboard:

      • <a href="#title-heading">Skip to content</a>
      • <a href="#breadcrumbs">Skip to breadcrumbs</a>
      • <a href="#header-menu-bar">Skip to header menu</a>
      • <a href="#navigation">Skip to action menu</a>
      • <a href="#quick-search-query">Skip to quick search</a>

      Why It Matters

      A link to jump over navigation or jump to the main content of the page assists keyboard users only if the link is properly functioning and is keyboard accessible.

      How to Fix It

      Ensure that the target for the link exists and that the link is not hidden with CSS display:none or visibility:hidden.

      Reference

      https://webaim.org/standards/508/checklist#standardo

            [CONFSERVER-54039] Section 508 - Broken skip links

            Thanks for your patience and interest in this issue. Please note that this issue has been superseded by CONFSERVER-74834 and skip links fixed in Confluence Server and Data Center 7.15.

            Makisa Appleton | Principal Product Manager, Confluence Server and Data Center

            Makisa Appleton added a comment - Thanks for your patience and interest in this issue. Please note that this issue has been superseded by CONFSERVER-74834  and skip links fixed in Confluence Server and Data Center 7.15. Makisa Appleton | Principal Product Manager, Confluence Server and Data Center

            Hi there,

             

            The Confluence team are currently looking into section 508 compliance as part of their accessibility roadmap. The best issue to watch, vote, and comment on regarding 508 compliance is CONFSERVER-12383 Further information about Atlassian's current stance on Accessibility can be found on https://www.atlassian.com/accessibility

            Cheers,

             

            Michael Andreacchio

            Michael Andreacchio added a comment - Hi there,   The Confluence team are currently looking into section 508 compliance as part of their accessibility roadmap. The best issue to watch, vote, and comment on regarding 508 compliance is  CONFSERVER-12383 Further information about Atlassian's current stance on Accessibility can be found on  https://www.atlassian.com/accessibility Cheers,   Michael Andreacchio

              Unassigned Unassigned
              btom1 Brian
              Affected customers:
              10 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: