-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
1
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
The following changes can be made to make Portfolio more accessible to people with disabilities:
- Make everything accessible via the keyboard. Includes
- Table column headers
- Expanding/collapsing table rows
- Re-ranking table rows
- Information displayed on mouse hover
- Reports
- Keyboard navigation should not become trapped in an input field
- Input fields should have names to inform blind users what field they are on
- Text-less buttons should have a name
Generally speaking, the goal is to reach Section 508 compliance.
- duplicates
-
JPOSERVER-1341 JIRA Portfolio backlog column settings not keyboard accessible
-
- Closed
-
-
JPOSERVER-1359 Inaccessible to keyboard-only users - accessibility
-
- Closed
-
-
JPOSERVER-1360 Keyboard Traps - Accessibility Jira Portfolio
-
- Closed
-
-
JPOSERVER-1361 Jira Portfolio Table Accessibility
-
- Closed
-
-
JPOSERVER-1362 No valid name or title information for buttons / images
-
- Closed
-
-
JPOSERVER-1363 Information only available via mouse-over
-
- Closed
-
- relates to
-
JRASERVER-61625 Cannot use the keyboard to navigate header dropdowns
-
- Closed
-
-
JRACLOUD-89328 Improve accessibility
- Closed
- links to
- mentioned in
-
Page Loading...
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center