Is JIRA and Confluence AODA Compliant ?

[Hussien Hammad]

We are reaching out to you regarding the accessibility of your applications JIRA/Confluence.  Our company uses your application and we must abide by AODA legislation (https://www.ontario.ca/laws/statute/05a11).  As such, applications in use must meet accessibility WCAG 2.0 Level AA Guidelines.

With that being said, Is your application accessible? If not, do you have plans and/or timelines for when your application will be made accessible?

If it is accessible, do you have existing accessibility compliance reports for your application? Can you share them please?

I am posting it here on the board as it seems I cannot locate "get help" email address to ask Atlassian directly.

Thank you for your time.

[Peter DeWitt]

@Susan Hauth (Toronto - JIRA Queen) , You're from up north.  Can you add any insight into this question?

@Hussien Hammad , for help, just open a support ticket with Atlassian. support.atlassian.com

[Charles Vanek]

Only parts of Jira and Confluence are accessible.  There are a lot of easy to fix WCAG issues along with more systemic ones.  Thus it is really dependent upon how it's used.

Example: Confluence's Search results should put the page links of results into a heading tag.  Easy fix.  

Jira's Boards can convey priority by position, however this position isn't perceivable and doesn't effect the Priority value of an issue in the form thus priority isn't filterable.  The workaround is to set Priority to convey Prioity like it is intended and assigning to a sprint then makes all things really easy.  The fix to Boards however I suspect is a systemic problem that will be hard to fix.

Use Atlassian products with caution if you need to comply or have a diverse workforce.