Critical Accessibility Issue

Hi,

I'm running qdPM V9 Beta.
Tasks, Tickets, Discussions, Tasks Groups, Versions, Phases, Reports under project, are not clickable with a keyboard since they are wrapped around <span> tag.
If you keep pressing tab in order to cycle through the clickable items, it skips all the controls mentioned above and jumps from project info to add comment.
This is same for the element that lets you choose a file and upload an attachment.
This is serious bug for users who use screen readers or can't use mouse.
It'd be great if this fix is implemented into both extended and free beta version.
If you like to keep span tag instead of changing them to button or links, , please look at the resources below.
2. Using WAI-ARIA
http://www.w3.org/TR/wai-aria/usage
5.4. Definition of Roles
http://www.w3.org/TR/wai-aria/roles
6.6. Definitions of States and Properties
http://www.w3.org/TR/wai-aria/states_and_properties
Thanks,

JL

[nunu]

Thanks.

Unfortunately the next version are almost complete and they have a completely new interface.

If you download the qdPM V9 Beta you can check it out.

Actually I'm running qdPM V9 Beta, so the bug exists in the beta.

FYI, if you want to test the UI for QDPM 9.0 with a screen reader,
Windows 10: Narrator (Press windoes+enter)
Windows: NVDA: (Open Source, more Advanced than Narrator)
http://www.nvaccess.org/
Mac: Voiceover (press command+f5)
Also you should tab around and make sure it highlight all the elements.
Hope it gets fixed!
Thanks,

[nunu]

Sorry we have no intention of making any changes to qdPM for accessibility at this stage.

I'm sorry, and it's very disappointing to hear that. Have you brought this issue to the team and discuss, or is this just assumed response of what the entire team would say?
I hope the qdpm team realizes the importance of accessibility.
Over 1 billion people (15% of world population) have some kind of disability, and it's the largest minority group.
Also, there are accessibility Procurement laws that prohibit companies and organizations from using inaccessible technology.
This will isolate many users from using QDPM.
I really hope the QDPM team seriously consider the accessibility.

Sorry we have no intention of making any changes to qdPM for accessibility at this stage.

[nunu]

I am speaking on behalf of the entire team.