• 13
    • 24
    • We collect Jira 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 Jira Server. Using Jira 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 Jira Server and Data Center.

      We have just published a refreshed VPAT document for Jira 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

       

            [JRASERVER-5574] Accessibility: Section 508 compliance

            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 Jira Server and Data Center.

            We have just published a refreshed VPAT document for Jira 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 Jira Server and Data Center. We have just published a refreshed VPAT document for Jira 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

            Dana Mi added a comment -

            Systems should be accessible using JWAS as well.

             

            Dana Mi added a comment - Systems should be accessible using JWAS as well.  

            Here are some major Jira Concerns using Voice Over on Mac (also present with JAWs on PC) from my company:

            1. When I try to tag someone, I can’t hear the suggestions (tagging them in comments)
            2. I cannot easily edit what I have written. For example, when I exit the comment text field then re-read my comment before posting, If I notice a spelling error or that I tagged someone incorrectly, I cannot edit my comment.  I can make changes if I keep my focus in the comment field the whole time, however, if I leave it, I cannot go back into it and edit. My focus will begin at the comment beginning no matter if I try navigating to the right spot via words or character navigation (keeps cursor at beginning and won’t move).
            3. Heading levels on the pages are out of order; not nested as she would expect
            4. When I expand a menu in the main navigation region, the expanded content doesn’t follow as the next thing in the reading order; can’t seem to find expanded options anywhere (HTML ordering issue?)
            5. When I focus on the Dashboards menu item, it says there is a shortcut key to view or manage dashboards. However, when I press the short cut key, it just moves me to the next item on the screen like I was pressing the tab key.  The other keyboard shortcuts for the other menu items don’t do anything at all. Hot keys don’t work intermittently
            6. I have found that table navigation in the past has not been easy. Navigating from row to row and column to column wasn’t consistent.  As a result, it is difficult to keep track of one’s place in the table. **This is something I remembered from the past but can’t find the example.  I rarely encounter tables when I use Jira day to day.  Left/right and up/down arrows within screen reader don’t move as expected.
            7. Lots of things announce as clickable. For example on teams’ dashboard pages under the description headings, “Defined,” “Block,” “In progress” “RFT” and etc. all announce as <h6> and clickable – not supposed to be?
            8. If I use Jira with Chrome, it logs me out every time I post a comment (doesn’t do with Safari, but does change focus to top of screen)
            9. On teams’ dashboard pages, there is an extensive use of inappropriate landmarks.  For instance it seems like the “main landmark” is used many many times. Landmarks used to call out what is the main content in the page. Would be helpful if they had more labeled landmarks. Makes page very noisy, navigation slow.

            Amy Leonard added a comment - Here are some major Jira Concerns using Voice Over on Mac (also present with JAWs on PC) from my company: When I try to tag someone, I can’t hear the suggestions (tagging them in comments) I cannot easily edit what I have written. For example, when I exit the comment text field then re-read my comment before posting, If I notice a spelling error or that I tagged someone incorrectly, I cannot edit my comment.  I can make changes if I keep my focus in the comment field the whole time, however, if I leave it, I cannot go back into it and edit. My focus will begin at the comment beginning no matter if I try navigating to the right spot via words or character navigation (keeps cursor at beginning and won’t move). Heading levels on the pages are out of order; not nested as she would expect When I expand a menu in the main navigation region, the expanded content doesn’t follow as the next thing in the reading order; can’t seem to find expanded options anywhere (HTML ordering issue?) When I focus on the Dashboards menu item, it says there is a shortcut key to view or manage dashboards. However, when I press the short cut key, it just moves me to the next item on the screen like I was pressing the tab key.  The other keyboard shortcuts for the other menu items don’t do anything at all. Hot keys don’t work intermittently I have found that table navigation in the past has not been easy. Navigating from row to row and column to column wasn’t consistent.  As a result, it is difficult to keep track of one’s place in the table. **This is something I remembered from the past but can’t find the example.  I rarely encounter tables when I use Jira day to day.  Left/right and up/down arrows within screen reader don’t move as expected. Lots of things announce as clickable. For example on teams’ dashboard pages under the description headings, “Defined,” “Block,” “In progress” “RFT” and etc. all announce as <h6> and clickable – not supposed to be? If I use Jira with Chrome, it logs me out every time I post a comment (doesn’t do with Safari, but does change focus to top of screen) On teams’ dashboard pages, there is an extensive use of inappropriate landmarks.  For instance it seems like the “main landmark” is used many many times. Landmarks used to call out what is the main content in the page. Would be helpful if they had more labeled landmarks. Makes page very noisy, navigation slow.

            Sukbhir, we prefer a solution that comes from Atlassian and becomes part of the Standard installation of Jira. Using additional software components increases costs and complexity because the components have to keep up with Jira updates. 

            Markus Geishüttner added a comment - Sukbhir, we prefer a solution that comes from Atlassian and becomes part of the Standard installation of Jira. Using additional software components increases costs and complexity because the components have to keep up with Jira updates. 

            Markus, Did you try Unstoppable for your accessibility requirements?

            Sukhbir Dhillon added a comment - Markus, Did you try  Unstoppable for your accessibility requirements?

            As a German company we need Jira to conform to (quote): "software ergonomics like usability, consistency and accessibility according to DIN EN ISO 9241 (Parts 11, 13-17, 110, 112, 125, 129, 143, 151, 154, 161, 171, 303, 306) and WCAG 2.1 Level AA (ISO/IEC 40500:2012)."

            A test of Jira found several areas where Jira does not conform, we created ticket GHS-163937 and the support team made us aware of this feature request

            Markus Geishüttner added a comment - As a German company we need Jira to conform to (quote): "software ergonomics like usability, consistency and accessibility according to DIN EN ISO 9241 (Parts 11, 13-17, 110, 112, 125, 129, 143, 151, 154, 161, 171, 303, 306) and WCAG 2.1 Level AA (ISO/IEC 40500:2012)." A test of Jira found several areas where Jira does not conform, we created ticket GHS-163937 and the support team made us aware of this feature request

            peter added a comment -

            HI everyone,

            Just a note to let you know we've had Jira Server and Data Center audited for compliance and published the report here https://confluence.atlassian.com/display/ACCESSIBILITY/Jira+Server+and+Data+Center+VPAT+for+Section+508+compliance

            This will help inform our improvements into Jira's accessibility.

            Peter

            peter added a comment - HI everyone, Just a note to let you know we've had Jira Server and Data Center audited for compliance and published the report here https://confluence.atlassian.com/display/ACCESSIBILITY/Jira+Server+and+Data+Center+VPAT+for+Section+508+compliance This will help inform our improvements into Jira's accessibility. Peter

            peter added a comment -

            Hi peter.macdonald3 we should have updated VPATs on  https://www.atlassian.com/accessibility by mid April.

            Best

            Peter

            peter added a comment - Hi peter.macdonald3 we should have updated VPATs on  https://www.atlassian.com/accessibility  by mid April. Best Peter

            Hi Peter

            Do you have any further details regarding progress of the updated VPATs. ATO (Aust Govt) are keen to obtain this information.

            Regards

            Peter Macdonald

            Peter Macdonald added a comment - Hi Peter Do you have any further details regarding progress of the updated VPATs. ATO (Aust Govt) are keen to obtain this information. Regards Peter Macdonald

            peter added a comment -

            I can provide an update to say we're working on getting updated VPATs for Confluence Server, Jira Server, JSD Server and Bitbucket Server. 

            peter added a comment - I can provide an update to say we're working on getting updated VPATs for Confluence Server, Jira Server, JSD Server and Bitbucket Server. 

              pwodkowski Pawel Wodkowski
              7ee5c68a815f Jeff Turner
              Votes:
              116 Vote for this issue
              Watchers:
              115 Start watching this issue

                Created:
                Updated:
                Resolved: