• Type: Bug
• Resolution: Fixed
• Priority: High (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 8.20.30, 9.12.2, 9.4.18
• Component/s: (Advanced Roadmaps) Accessibility
• Labels:

  • 4.1.2
  • A11Y-430
  • Level-A
  • WCAG21
  • ax-at-JAWS
  • ax-at-user
  • ax-bug
  • ax-customer-escalated
  • ax-desktop
  • ax-esc-lloyds
  • ax-high-priority
  • ax-jiradc-arj
  • ax-jiradc-vpat-AccessibilityAssesmentRoadmaps
  • ax-qa
  • ax-qa-fixed
  • ax-qa-verified
  • ax-windows-chrome

1. 

   Screenshot 2024-07-19 at 1.19.46 PM.png

   656 kB

   19/Jul/2024 7:50 AM

[JSWSERVER-25834] Accessibility Assessment - Roadmaps: Disable state not announced for the screen Reader user

Anoop Ashok Goudar (Inactive) made changes - 29/Jul/2024 10:03 AM

Resolution		New: Fixed [ 1 ]
Status	Original: Ready for Development [ 10049 ]	New: Closed [ 6 ]

Collapse comment: Anoop Ashok Goudar (Inactive) added a comment - 29/Jul/2024 10:03 AM

Anoop Ashok Goudar (Inactive) added a comment - 29/Jul/2024 10:03 AM

Issue has been fixed with the latest code.

Expand comment: Anoop Ashok Goudar (Inactive) added a comment - 29/Jul/2024 10:03 AM

Anoop Ashok Goudar (Inactive) added a comment - 29/Jul/2024 10:03 AM Issue has been fixed with the latest code.

Anoop Ashok Goudar (Inactive) made changes - 29/Jul/2024 8:37 AM

Assignee

Original: Stasiu [ ddudziak ]

New: Anoop Ashok Goudar [ 8809c27e584c ]

Sameer Shaikh made changes - 26/Jul/2024 10:37 AM

Labels

Original: 4.1.2 A11Y-430 Level-A WCAG21 ax-at-JAWS ax-at-user ax-bug ax-customer-escalated ax-desktop ax-esc-lloyds ax-high-priority ax-jiradc-arj ax-jiradc-vpat-AccessibilityAssesmentRoadmaps ax-qa ax-windows-chrome

New: 4.1.2 A11Y-430 Level-A WCAG21 ax-at-JAWS ax-at-user ax-bug ax-customer-escalated ax-desktop ax-esc-lloyds ax-high-priority ax-jiradc-arj ax-jiradc-vpat-AccessibilityAssesmentRoadmaps ax-qa ax-qa-fixed ax-qa-verified ax-windows-chrome

Rahil Shaikh made changes - 19/Jul/2024 7:51 AM

Description

Original: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Sceenshot !Screenshot 2024-07-19 at 1.19.46 PM.png|width=347,height=158! h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

New: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Screenshot !Screenshot 2024-07-19 at 1.19.46 PM.png|width=347,height=158! h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

Rahil Shaikh made changes - 19/Jul/2024 7:51 AM

Description

Original: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Sceenshot !Screenshot 2024-07-19 at 1.19.46 PM.png! h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

New: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Sceenshot !Screenshot 2024-07-19 at 1.19.46 PM.png|width=347,height=158! h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

Rahil Shaikh made changes - 19/Jul/2024 7:50 AM

Description

Original: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

New: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Sceenshot !Screenshot 2024-07-19 at 1.19.46 PM.png! h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

Rahil Shaikh made changes - 19/Jul/2024 7:50 AM

Attachment

New: Screenshot 2024-07-19 at 1.19.46 PM.png [ 460828 ]

Rahil Shaikh made changes - 19/Jul/2024 7:48 AM

Description

Original: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

New: h3. Issue Summary Disable state is not announced for the options such as "Epic" and "Story". h3. Steps to Reproduce  # Navigate to the "Plans" dropdown and activate it.  # Select any option from the list.  # Using the screen reader, navigate to the mentioned button in the main content area and activate it.  # Listen that the state is not announced for the options. h3. Actual Results The "Epic" and "Story" options do not convey their disabled state when the user navigates using the JAWS screen reader. This is because these elements use role="menu" and role="menuitem" attributes. As well, the "Epic" and "Story" interactive elements are announced together. As a result, screen reader users are not able to understand the button's disabled state. h3. Expected Results  * Remove roles "menu" and "menuitem" from the mentioned instances.  * Code the "Epic" and "Story" options with native HTML <button> tag. Alternatively, use the role="button".  * Make sure that when the "Epic" and "Story" options are enabled, they receive keyboard focus using arrow keys. h3. Workaround Currently there is no known workaround for this behaviour. h3. Environment MacBook Pro (16-inch, 2019) macOS 14.3 (23D56) Chrome - Version 121.0.6167.184 Firefox- Version 122.0.1 (64-bit) Safari- Version 16.5.2 (18615.2.9.11.10) JAWS- Version 2024 NVDA- Version 2023.3 Voiceover - Version Latest

Marc Dacanay made changes - 12/Jul/2024 6:22 AM

Remote Link

New: This issue links to "Page (Confluence)" [ 926115 ]

Load more older events