-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 8.20.1
-
Component/s: Accessibility
-
- 4.1.2
- AXSR-22
- Level-A
- WCAG21
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-critical
- ax-critical-priority
- ax-customer-escalated
- ax-desktop
- ax-dev-ready
- ax-esc-tel
- ax-jira
- ax-jiradc-viewissue
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-prioritised
- ax-qa-verified
- ax-triaged
- ax-windows-chrome
- ax-windows-firefox
-
8.2
-
Severity 3 - Minor
Issue Description
In the “Add comment“ modal dialog, the “Add“ input element and “Cancel“ are programmatically coded incorrectly, since visually and functionality behave like a button.
Platform: Jira DC
Version: 8.22.1
Steps to Reproduce
- Navigate to the main content area in the Comments section and Activate - the “Add comments“ link.
- Type a comment in the input field and then navigate to the “Add“ and “Cancel“ links.
Screenshot

Actual Behaviour
In the “Add comment“ modal dialog, the “Add” element is coded into an input attribute and the “Cancel“ element is coded into an anchor attribute. This develops confusion for the screen reader user as the elements are announced as a link, but their behaviour is like a button element.
Expected Result
Programmatically the elements should be coded into an <button> attribute or a role=” button” should be provided to the elements. The screen reader would be confused between a link and a button. The functionality would be more clear when the element is coded into a button since it behaves like a button.
- is related to
-
JRASERVER-74372 Project issues: The "Add" button receives screen reader focus when disabled and announced inappropriately.
-
- Closed
-