-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
9.12.2
-
9.12
-
Severity 3 - Minor
-
Issue Summary
Striked-through text is not conveyed and is not announced for the screen reader users.
Note: A similar issue has been found on the "Backlog" page. Refer to screenshot 2 for reference
Steps to Reproduce
- Open the "Scrum board" page.
- Using the screen reader, navigate to the strike-through content.
- Listen that no announcement has been made by the screen reader for the strike-through text.
Screen Recording
Screen Recording 2024-02-06 at 3.21.06 PM.mov
Screenshot 1: Scrum board
Screenshot 2: Backlog
Actual Results
When the user navigates to an issue that has a strike-through on it, the screen reader announces it as “SSPA-15”, "SSPA-16", and "SSPA-17". It can visually convey that these issues are cancelled/deleted because of a strike-through on the issue but for screen reader users it does not announce that this issue is completed.
As a result screen reader users will not be aware of this and cannot interact with it effectively.
Expected Results
The issue that has a strike-through should be announced as a “Cancelled/deleted issue” which will help screen reader users to understand the status of the issue. For this, an "aria-label" can be provided which will resolve this issue.
Code Example:
<a href="/browse/SSPA-15" aria-label="Cancelled SSPA-15 issue" title="SSPA-15" class="js-key-link ghx-key-link" tabindex="0" aria-describedby="kanban-issue-key-instruction"> <span class="ghx-issue-key-link"> <span class="js-key-link ghx-key-link-project-key">SSPA</span> <span class="js-key-link ghx-key-link-issue-num">-15</span> </span> </a>
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOs Sonoma 14.3
Chrome - Version 120.0.6099.109 (Official Build) (arm64)
Firefox- Version 92.0 (64-bit)
Safari- Version 17.3 (19617.2.4.11.8)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
[JSWSERVER-26226] Scrum board: Strike-through content not announced for the screen reader user
| Labels | Original: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jira-dc-vpat ax-jira-dc-vpat-Backlog ax-jiradc-vpat2024 ax-jiradc-vpat2024-backlog ax-jiradc-vpat2024-pg09 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa | New: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jira-dc-vpat ax-jira-dc-vpat-Backlog ax-jira-dc-vpat-ScrumBoard ax-jiradc-vpat2024 ax-jiradc-vpat2024-backlog ax-jiradc-vpat2024-pg09 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa |
| Labels | Original: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-backlog ax-jiradc-vpat2024-pg09 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa | New: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jira-dc-vpat ax-jira-dc-vpat-Backlog ax-jiradc-vpat2024 ax-jiradc-vpat2024-backlog ax-jiradc-vpat2024-pg09 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa |
| Component/s | Original: Accessibility - Future VPAT consideration [ 74493 ] | |
| Component/s | New: Scrum Board [ 55619 ] | |
| Component/s | New: Backlog [ 46795 ] | |
| Component/s | New: Accessibility [ 62491 ] | |
| Key | Original: JRASERVER-77247 | New: JSWSERVER-26226 |
| Affects Version/s | Original: 9.12.2 [ 106456 ] | |
| Affects Version/s | New: 9.12.2 [ 106455 ] | |
| Project | Original: Jira Data Center [ 10240 ] | New: Jira Software Data Center [ 12200 ] |
| Priority | Original: High [ 2 ] | New: Medium [ 3 ] |
| Component/s | Original: Accessibility [ 62490 ] | |
| Component/s | New: Accessibility - Future VPAT consideration [ 74493 ] |
| Labels | Original: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa | New: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-backlog ax-jiradc-vpat2024-pg09 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa |
| Description |
Original:
h3. Issue Summary
Striked-through text is not conveyed and is not announced for the screen reader users. Note: A similar issue has been found on the "Backlog" page, refer screenshot 2 h3. Steps to Reproduce # Open the "Scrum board" page. # Using the screen reader, navigate to the strike-through content. # Listen that no announcement has been made by the screen reader for the strike-through text. h3. Screen Recording [^Screen Recording 2024-02-06 at 3.21.06 PM.mov] h3. Screenshot 1: Scrum board !Screenshot 2024-02-06 at 3.24.30 PM.png|width=518,height=313! h3. Screenshot 2: Backlog !Screenshot 2024-02-20 at 1.07.51 PM.png|width=519,height=284! h3. Actual Results When the user navigates to an issue that has a strike-through on it, the screen reader announces it as “SSPA-15”, "SSPA-16", and "SSPA-17". It can visually convey that these issues are cancelled/deleted because of a strike-through on the issue but for screen reader users it does not announce that this issue is completed. As a result screen reader users will not be aware of this and cannot interact with it effectively. h3. Expected Results The issue that has a strike-through should be announced as a “Cancelled/deleted issue” which will help screen reader users to understand the status of the issue. For this, an "aria-label" can be provided which will resolve this issue. *Code Example:* {code:java} <a href="/browse/SSPA-15" aria-label="Cancelled SSPA-15 issue" title="SSPA-15" class="js-key-link ghx-key-link" tabindex="0" aria-describedby="kanban-issue-key-instruction"> <span class="ghx-issue-key-link"> <span class="js-key-link ghx-key-link-project-key">SSPA</span> <span class="js-key-link ghx-key-link-issue-num">-15</span> </span> </a>{code} h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2021) macOs Sonoma 14.3 Chrome - Version 120.0.6099.109 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.3 (19617.2.4.11.8) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
New:
h3. Issue Summary
Striked-through text is not conveyed and is not announced for the screen reader users. *Note:* A similar issue has been found on the "Backlog" page. Refer to screenshot 2 for reference h3. Steps to Reproduce # Open the "Scrum board" page. # Using the screen reader, navigate to the strike-through content. # Listen that no announcement has been made by the screen reader for the strike-through text. h3. Screen Recording [^Screen Recording 2024-02-06 at 3.21.06 PM.mov] h3. Screenshot 1: Scrum board !Screenshot 2024-02-06 at 3.24.30 PM.png|width=518,height=313! h3. Screenshot 2: Backlog !Screenshot 2024-02-20 at 1.07.51 PM.png|width=519,height=284! h3. Actual Results When the user navigates to an issue that has a strike-through on it, the screen reader announces it as “SSPA-15”, "SSPA-16", and "SSPA-17". It can visually convey that these issues are cancelled/deleted because of a strike-through on the issue but for screen reader users it does not announce that this issue is completed. As a result screen reader users will not be aware of this and cannot interact with it effectively. h3. Expected Results The issue that has a strike-through should be announced as a “Cancelled/deleted issue” which will help screen reader users to understand the status of the issue. For this, an "aria-label" can be provided which will resolve this issue. *Code Example:* {code:java} <a href="/browse/SSPA-15" aria-label="Cancelled SSPA-15 issue" title="SSPA-15" class="js-key-link ghx-key-link" tabindex="0" aria-describedby="kanban-issue-key-instruction"> <span class="ghx-issue-key-link"> <span class="js-key-link ghx-key-link-project-key">SSPA</span> <span class="js-key-link ghx-key-link-issue-num">-15</span> </span> </a>{code} h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2021) macOs Sonoma 14.3 Chrome - Version 120.0.6099.109 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.3 (19617.2.4.11.8) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
| Description |
Original:
h3. Issue Summary
Striked-through text is not conveyed and is not announced for the screen reader users. h3. Steps to Reproduce # Open the "Scrum board" page. # Using the screen reader, navigate to the strike-through content. # Listen that no announcement has been made by the screen reader for the strike-through text. h3. Screen Recording [^Screen Recording 2024-02-06 at 3.21.06 PM.mov] h3. Screenshot !Screenshot 2024-02-06 at 3.24.30 PM.png|width=518,height=313! h3. Actual Results When the user navigates to an issue that has a strike-through on it, the screen reader announces it as “SSPA-15”, "SSPA-16", and "SSPA-17". It can visually convey that these issues are cancelled/deleted because of a strike-through on the issue but for screen reader users it does not announce that this issue is completed. As a result screen reader users will not be aware of this and cannot interact with it effectively. h3. Expected Results The issue that has a strike-through should be announced as a “Cancelled/deleted issue” which will help screen reader users to understand the status of the issue. For this, an "aria-label" can be provided which will resolve this issue. *Code Example:* {code:java} <a href="/browse/SSPA-15" aria-label="Cancelled SSPA-15 issue" title="SSPA-15" class="js-key-link ghx-key-link" tabindex="0" aria-describedby="kanban-issue-key-instruction"> <span class="ghx-issue-key-link"> <span class="js-key-link ghx-key-link-project-key">SSPA</span> <span class="js-key-link ghx-key-link-issue-num">-15</span> </span> </a>{code} h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2021) macOs Sonoma 14.3 Chrome - Version 120.0.6099.109 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.3 (19617.2.4.11.8) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
New:
h3. Issue Summary
Striked-through text is not conveyed and is not announced for the screen reader users. Note: A similar issue has been found on the "Backlog" page, refer screenshot 2 h3. Steps to Reproduce # Open the "Scrum board" page. # Using the screen reader, navigate to the strike-through content. # Listen that no announcement has been made by the screen reader for the strike-through text. h3. Screen Recording [^Screen Recording 2024-02-06 at 3.21.06 PM.mov] h3. Screenshot 1: Scrum board !Screenshot 2024-02-06 at 3.24.30 PM.png|width=518,height=313! h3. Screenshot 2: Backlog !Screenshot 2024-02-20 at 1.07.51 PM.png|width=519,height=284! h3. Actual Results When the user navigates to an issue that has a strike-through on it, the screen reader announces it as “SSPA-15”, "SSPA-16", and "SSPA-17". It can visually convey that these issues are cancelled/deleted because of a strike-through on the issue but for screen reader users it does not announce that this issue is completed. As a result screen reader users will not be aware of this and cannot interact with it effectively. h3. Expected Results The issue that has a strike-through should be announced as a “Cancelled/deleted issue” which will help screen reader users to understand the status of the issue. For this, an "aria-label" can be provided which will resolve this issue. *Code Example:* {code:java} <a href="/browse/SSPA-15" aria-label="Cancelled SSPA-15 issue" title="SSPA-15" class="js-key-link ghx-key-link" tabindex="0" aria-describedby="kanban-issue-key-instruction"> <span class="ghx-issue-key-link"> <span class="js-key-link ghx-key-link-project-key">SSPA</span> <span class="js-key-link ghx-key-link-issue-num">-15</span> </span> </a>{code} h3. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available h3. Environment MacBook Pro (16-inch, 2021) macOs Sonoma 14.3 Chrome - Version 120.0.6099.109 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.3 (19617.2.4.11.8) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
| Attachment | New: Screenshot 2024-02-20 at 1.07.51 PM.png [ 452443 ] |
| Labels | Original: 4.1.2 Level-A WCAG21 ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa | New: 4.1.2 Level-A WCAG21 a11y-triaged ax-at-JAWS ax-at-NVDA ax-at-VO ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-pg20 ax-jiradc-vpat2024-scrumboard ax-qa |