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.

This problem will be investigated on the bug *https://jira.atlassian.com/browse/JRASERVER-73585*

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.

Workaround.

Currently there is no know workaround for this behavior.