• 19
    • 24
    • 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.

      Thanks

      Makisa | Principal Product Manager, Data Center Products

       


      Make Confluence Section 508 accessibility standard compliant.

      http://www.section508.gov/

      Indicative of the requirements are in the Voluntary Product Accessibility Template (VPAT) for Web-based Internet information and applications:

      (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
      (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
      (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
      (d) Documents shall be organized so they are readable without requiring an associated style sheet.
      (e) Redundant text links shall be provided for each active region of a server-side image map.
      (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
      (g) Row and column headers shall be identified for data tables.
      (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
      Frames shall be titled with text that facilitates frame identification and navigation
      (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
      (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
      (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.
      (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
      When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
      (o) A method shall be provided that permits users to skip repetitive navigation links.

      Jira has a request here: http://jira.atlassian.com/browse/JRA-5574

            [CONFSERVER-12383] Section 508 Compliance for Confluence (VPAT)

            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.

            Thanks

            Makisa | Principal Product Manager, Data Center Products

            Makisa Appleton added a comment - 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 . Thanks Makisa | Principal Product Manager, Data Center Products

            Is there a road map as Luis had mentioned above?

            --Brandon

            Brandon Viertel added a comment - Is there a road map as Luis had mentioned above? --Brandon

            I'm glad you provided an updated VPAT. I really look forward to progress on all the related tickets to address the accessibility shortcomings.

            I see that most are tagged with a "Gathering Interest" status. I assume that means you want us all to vote up items more important to address.

            I don't see any tagged as "In Progress". Can we expect any movement without more votes? Is there a roadmap to address the issues?

             

            Luis Menchu added a comment - I'm glad you provided an updated VPAT. I really look forward to progress on all the related tickets to address the accessibility shortcomings. I see that most are tagged with a "Gathering Interest" status. I assume that means you want us all to vote up items more important to address. I don't see any tagged as "In Progress". Can we expect any movement without more votes? Is there a roadmap to address the issues?  

            peter added a comment -

            Hi everyone,

            Just a note to say we've published an update VPAT for 508 compliance here https://confluence.atlassian.com/display/ACCESSIBILITY/Confluence+Server+and+Data+Center+VPAT+for+Section+508+compliance

            This will help inform future Accessibility improvements for Confluence Server.

            Peter

            peter added a comment - Hi everyone, Just a note to say we've published an update VPAT for 508 compliance here https://confluence.atlassian.com/display/ACCESSIBILITY/Confluence+Server+and+Data+Center+VPAT+for+Section+508+compliance This will help inform future Accessibility improvements for Confluence Server. Peter

            @zlmitche @pscobie, if I were Atlassian, I would apply for the VPAT 2.2 INT as it covers WCAG 2.0, Section 508 Refresh, and The EU's standard ( EN 301 549). 

            Link to the VPAT: https://www.itic.org/policy/accessibility/vpat

            What is a VPAT per Section 508: https://www.section508.gov/sell/vpat

            What is a VPAT per Bureau of Internet Accessibility: https://www.boia.org/blog/what-is-a-vpat-and-how-is-it-used

             

            Carlos Andrews added a comment - @zlmitche @pscobie, if I were Atlassian, I would apply for the VPAT 2.2 INT as it covers WCAG 2.0, Section 508 Refresh, and The EU's standard (  EN 301 549 ).  Link to the VPAT: https://www.itic.org/policy/accessibility/vpat What is a VPAT per Section 508: https://www.section508.gov/sell/vpat What is a VPAT per Bureau of Internet Accessibility: https://www.boia.org/blog/what-is-a-vpat-and-how-is-it-used  

            Hello Peter,
            Thank you for the update on the VPAT, as you may know many of us find this issue very important. Since this is the 508 ticket, which has been superseded by WCAG 2.0. Is there intent to update the VPAT to cover WCAG 2.0 as well and hopefully the issues found to be involved in a sprint soon after? This issue has been on your radar for 10 years now and solutions have been provided in many tickets.

            Zach

            Zach Mitchell added a comment - Hello Peter, Thank you for the update on the VPAT, as you may know many of us find this issue very important. Since this is the 508 ticket, which has been superseded by WCAG 2.0. Is there intent to update the VPAT to cover WCAG 2.0 as well and hopefully the issues found to be involved in a sprint soon after? This issue has been on your radar for 10 years now and solutions have been provided in many tickets. Zach

            Zach Mitchell added a comment - - edited

            I have provided accessibility modifications for Confluence 6.4.3 and 6.13.0, which you can find in the related issues of this ticket, and the WCAG Ticket.

            If anyone has time please test these adjustments and vote on each of the issues to get Atlassian's attention.

            Full github repository is here 

             

            Zach

            Zach Mitchell added a comment - - edited I have provided accessibility modifications for Confluence 6.4.3 and 6.13.0, which you can find in the related issues of this ticket, and the WCAG Ticket. If anyone has time please test these adjustments and vote on each of the issues to get Atlassian's attention. Full github repository is here    Zach

            Update to all watchers not in the WCAG Compliance ticket I have updated my post there in which you can use JavaScript and CSS to meet WCAG AA (and 508).

            Zach Mitchell added a comment - Update to all watchers not in the WCAG Compliance ticket  I have updated my post there in which you can use JavaScript and CSS to meet WCAG AA (and 508).

            @StephenGramm: I'm a government contractor as well and do Section 508 compliance. In regards to the plugins in the Atlassian Marketplace, Atlassian's Vendor approval process does not have Section 508 testing at all. WCAG 2.0 A/AA compliance needs to be done by Jan 18, 2018, per this document: https://www.federalregister.gov/documents/2017/01/18/2017-00395/information-and-communication-technology-ict-standards-and-guidelines. 

            Carlos Andrews added a comment - @StephenGramm: I'm a government contractor as well and do Section 508 compliance. In regards to the plugins in the Atlassian Marketplace, Atlassian's Vendor approval process does not have Section 508 testing at all. WCAG 2.0 A/AA compliance needs to be done by Jan 18, 2018, per this document: https://www.federalregister.gov/documents/2017/01/18/2017-00395/information-and-communication-technology-ict-standards-and-guidelines.  

            Perhaps this will be discussed at the Atlassian Government Symposium

            Matt Boesch added a comment - Perhaps this will be discussed at the Atlassian Government Symposium . 

              mappleton@atlassian.com Makisa Appleton
              achowdhury Adnan Chowdhury [Atlassian]
              Votes:
              100 Vote for this issue
              Watchers:
              95 Start watching this issue

                Created:
                Updated:
                Resolved: