-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.30, 9.12.2, 9.4.17
-
8.2
-
Severity 3 - Minor
-
Issue Summary
The buttons present in the table section is not keyboard operable.
Steps to Reproduce
- Navigate to the "Plans" dropdown and select any plan.
- Navigate the table section using keyboard.
- Verify that the buttons present in the table is not accessible by keyboard.
Screenshot
Actual Results
The "Assignee", "Target start", "Target end", and "Status" buttons in table section is not operable with a keyboard. The role and state of the button is not programmatically determined for screen reader users. This made it difficult for keyboard-only and screen reader users to access the functionality associated with mentioned button.
Expected Results
Apply the following changes:
- Code the mentioned button using <button> tag.
- Provide 'aria-pressed' attribute to define a state of the button.
- Ensure that the mentioned buttons are accessible using keyboard and screen reader.
A working example of accessible button can be found at https://www.w3.org/WAI/ARIA/apg/patterns/button/
Code Snippet
<button data-name="section-none" class="_3WCnc" style="width: 176px;" aria-pressed="true">(...)<span class="_Mq3F">Target start</span>(...)</button>
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2019)
macOS Ventura Version 13.6.1
Chrome - Version 120.0.6099.234 (Official Build) (x86_64)
Firefox- Version 112.0.1 (64-bit)
Safari- Version 17.3 (18617.2.4.11.9, 18617)
JAWS- Version 2022
NVDA- Version 2020.3
- links to
[JSWSERVER-25750] Accessibility Assessment - Roadmaps: Buttons not operable with a keyboard
| Labels | Original: 2.1.1 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg03 ax-kb-user ax-qa | New: 2.1.1 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg03 ax-kb-user ax-qa ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 963921 ] |
| Priority | Original: High [ 2 ] | New: Medium [ 3 ] |
| Introduced in Version | Original: 9.12 | New: 8.2 |
| Affects Version/s | New: 8.20.30 [ 106364 ] | |
| Affects Version/s | New: 9.4.17 [ 106909 ] |
| Labels | Original: 2.1.1 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg03 ax-kb-user ax-qa | New: 2.1.1 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg03 ax-kb-user ax-qa |
| Component/s | Original: Accessibility [ 62491 ] | |
| Component/s | Original: (Advanced Roadmaps) Other [ 73719 ] | |
| Component/s | New: (Advanced Roadmaps) Accessibility [ 74392 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Ready for Development [ 10049 ] |
| Component/s | New: (Advanced Roadmaps) Other [ 73719 ] |
| Description |
Original:
h3. Issue Summary
The buttons present in the table section is not keyboard operable. h3. Steps to Reproduce # Navigate to the "Plans" dropdown and select any plan. # Navigate the table section using keyboard. # Verify that the buttons present in the table is not accessible by keyboard. h3. Screenshot !image-2024-02-07-13-12-23-528.png|thumbnail! h3. Actual Results The "Assignee", "Target start", "Target end", and "Status" buttons in table section is not operable with a keyboard. The role and state of the button is not programmatically determined for screen reader users. This made it difficult for keyboard-only and screen reader users to access the functionality associated with mentioned button. h3. Expected Results Apply the following changes: * Code the mentioned button using <button> tag. * Provide 'aria-selected' attribute to define a state of the button. * Ensure that the mentioned buttons are accessible using keyboard and screen reader. A working example of accessible button can be found at [https://www.w3.org/WAI/ARIA/apg/patterns/button/] *Code Snippet* {code:java} <button data-name="section-none" class="_3WCnc" style="width: 176px;" aria-selected="true">(...)<span class="_Mq3F">Target start</span>(...)</button>{code} h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2019) macOS Ventura Version 13.6.1 Chrome - Version 120.0.6099.234 (Official Build) (x86_64) Firefox- Version 112.0.1 (64-bit) Safari- Version 17.3 (18617.2.4.11.9, 18617) JAWS- Version 2022 NVDA- Version 2020.3 |
New:
h3. Issue Summary
The buttons present in the table section is not keyboard operable. h3. Steps to Reproduce # Navigate to the "Plans" dropdown and select any plan. # Navigate the table section using keyboard. # Verify that the buttons present in the table is not accessible by keyboard. h3. Screenshot !image-2024-02-07-13-12-23-528.png|thumbnail! h3. Actual Results The "Assignee", "Target start", "Target end", and "Status" buttons in table section is not operable with a keyboard. The role and state of the button is not programmatically determined for screen reader users. This made it difficult for keyboard-only and screen reader users to access the functionality associated with mentioned button. h3. Expected Results Apply the following changes: * Code the mentioned button using <button> tag. * Provide 'aria-pressed' attribute to define a state of the button. * Ensure that the mentioned buttons are accessible using keyboard and screen reader. A working example of accessible button can be found at [https://www.w3.org/WAI/ARIA/apg/patterns/button/] *Code Snippet* {code:java} <button data-name="section-none" class="_3WCnc" style="width: 176px;" aria-pressed="true">(...)<span class="_Mq3F">Target start</span>(...)</button>{code} h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2019) macOS Ventura Version 13.6.1 Chrome - Version 120.0.6099.234 (Official Build) (x86_64) Firefox- Version 112.0.1 (64-bit) Safari- Version 17.3 (18617.2.4.11.9, 18617) JAWS- Version 2022 NVDA- Version 2020.3 |
| Priority | Original: Low [ 4 ] | New: High [ 2 ] |