Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-14249

Improve accessibility by satisfying WAI-WCAG


    • 28
    • 22
    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.


      Atlassian update - March 2022

      Hi everyone

      Thank you for your interest in this issue by either voting, commenting or watching. We may be closing this issue but are continuing with our efforts to update accessibility in Confluence Server and Data Center.

      We have just published a refreshed VPAT document for Confluence Server and Data Center and the Data Center apps, Team Calendars for Confluence, Questions for Confluence and Analytics for Confluence that you can find here: Atlassian Accessibility.

      Ensuring we have an up-to-date VPAT is just the first step. In place of this ticket, we are creating detailed accessibility issues that can be watched and tracked. We’ll make sure to include resolved issues in release notes.

      For further details, you may also be interested in reading this post on Community: Updated VPAT documents are available for Data Center products.


      Makisa | Principal Product Manager, Data Center Products


      Confluence does not currently meet the Web Content Accessibility Guidelines (WAI-WCAG). In order for a growing number of governments to make use of Confluence, it would need to meet at least priority A and preferably priority AA of the standards.

      The list of countries in which this is a requirement is growing and includes:

      1. The Australian government
      2. The Canadian government
      3. The German government
      4. The United States government (section 508)

      Additionally, the space tools menu in the bottom left of the page can be opened and closed with a keyboard but there is no keyboard functionality for the items in the space tools menu. Pressing the up or down keyboard arrows or the enter key will open the menu but the focus is then not put on the menu and pressing tab will move you to the next page element instead of accessing the items in the menu.

      Also when accessing dialogs like the "Keyboard Shortcuts", Other Macros or While modifying a macro's content in the main section, the right side of the dialog box is not able to be navigated via the keyboard. Pressing the up or down arrow or the enter key will change the focus of the items in the filter navigation but the focus is then not put on the main content that is being updated even with subsequent tabs or arrows presses.

      Both of these are accessibility issues that cannot be resolved through Javascript and CSS and are very disruptive.

            Unassigned Unassigned
            amohdaris Azwandi Mohd Aris (Inactive)
            86 Vote for this issue
            92 Start watching this issue