• Type: Bug
• Resolution: Duplicate
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 8.13.3, 8.18.0
• Component/s: Accessibility, Board configuration
• Labels:

  • accessibility
  • ax-qa-ready

[JSWSERVER-20017] Atlassian list the Agile to be accessibility compliant, however this is not the case.

Matthew Brennan made changes - 28/Jun/2022 5:50 AM

Resolution		New: Duplicate [ 3 ]
Status	Original: Gathering Impact [ 12072 ]	New: Closed [ 6 ]

ssuryavanshi (Inactive) made changes - 28/Jun/2022 5:47 AM

Labels

Original: accessibility

New: accessibility ax-qa-ready

Murakami [Atlassian Support] made changes - 27/Jun/2022 2:43 PM

Description

Original: Items that are in WCAG2.0 that need to be considered on the Agile board to make it compliant: Principle 2 – Operable User interface components and navigation must be operable. Section 2.1.1 – Keyboard: Level a. Make all functionality available from a keyboard. Issue: If the user can not detect which column an item is in programmatically, and can not drag the item between columns using a mouse, it has failed to meet the keyboard operable criteria. 2.4.6 Headings and Labels. Level AA. Headings or labels describe the topic or purpose. Issue: The agile board has one heading for each column that the user can see. However the screen reader sees the headings as an ordered list: list of 3 items heading level 2 TO DO heading level 2 IN PROGRESS heading level 2 DONE These headings fail to identify the sections they represent. Each ticket associated to a stage should appear under its specific heading. For example: heading level 2 TO DO TEST-1234 assigned to: J. Smith. Status: Ready for QA heading level 2 IN PROGRESS TEST-1235 assigned to: J. Smith. Status: In QA The section headings are totally unusable for their purpose. This is currently in all versions. h3. Workaround. Currently there is no know workaround for this behavior.

New: Items that are in WCAG2.0 that need to be considered on the Agile board to make it compliant: Principle 2 – Operable User interface components and navigation must be operable. _Section 2.1.1 – Keyboard:_ _Level a._ _Make all functionality available from a keyboard._ _Issue: If the user can not detect which column an item is in programmatically, and can not drag the item between columns using a mouse, it has failed to meet the keyboard operable criteria._ {color:#4c9aff}This problem will be investigated on the bug *https://jira.atlassian.com/browse/JRASERVER-73585*{color} 2.4.6 Headings and Labels. Level AA. Headings or labels describe the topic or purpose. Issue: The agile board has one heading for each column that the user can see. However the screen reader sees the headings as an ordered list: list of 3 items heading level 2 TO DO heading level 2 IN PROGRESS heading level 2 DONE These headings fail to identify the sections they represent. Each ticket associated to a stage should appear under its specific heading. For example: heading level 2 TO DO TEST-1234 assigned to: J. Smith. Status: Ready for QA heading level 2 IN PROGRESS TEST-1235 assigned to: J. Smith. Status: In QA The section headings are totally unusable for their purpose. This is currently in all versions. h3. Workaround. Currently there is no know workaround for this behavior.

Murakami [Atlassian Support] made changes - 31/May/2022 5:45 PM

Link

New: This issue duplicates JRASERVER-73585 [ JRASERVER-73585 ]

SET Analytics Bot made changes - 31/May/2022 2:18 AM

UIS

Original: 1

New: 2

ssuryavanshi (Inactive) made changes - 27/May/2022 5:14 AM

Remote Link

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

ssuryavanshi (Inactive) made changes - 24/May/2022 6:36 AM

Remote Link

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

Makisa Appleton made changes - 04/Feb/2022 4:59 AM

Component/s

New: Accessibility [ 62491 ]

SET Analytics Bot made changes - 05/Jan/2022 4:31 AM

UIS

Original: 4

New: 1

SET Analytics Bot made changes - 23/Dec/2021 2:47 AM

UIS

Original: 1

New: 4

Load more older history items