-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 8.20.1
-
Component/s: Accessibility
-
- 2.4.3
- 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“ section, for the “Add” button link element, the screen reader receives focus even when there is no text in the input field to submit and the link is in the disabled state.
Platform: Jira DC
Version: 8.22.1
Steps to Reproduce
- Navigate to the main content area keeping the screen reader on, Navigate to the “Add comment“ link and activate it.
- In the “Add comment” section navigate to the Add button link without typing anything into the input field.
Screen Recording
Screen Recording 2022-03-29 at 6.15.53 PM.mov![]()
Actual Behaviour
In the “Add comment“ section, for the “Add” button link element, the screen reader receives focus even when there is no text in the input field to submit and the link is in the disabled state. On activating the comment section is closed which is not functionality-wise correct. Additionally, it announces “Dimmed“ to the voice-over instead of “Disabled“ which will confuse the screen reader user.
Expected Result
The “Add“ link should not receive keyboard as well as screen reader focus, in additionally it should be announced as “Button Disabled“. The button link should not get activated since it is disabled. An aria-disabled could be given to the element so that its state indicates that the element is perceivable but disabled, so it is not editable or otherwise operable.
- relates to
-
JRASERVER-74374 Project issues: Anchor and input elements defined inappropriately to the visually appearing Button elements
-
- Closed
-