Hello!
I’m reaching out to connect with any folks who are interested in, or are working to advance, accessibility in Asana.
Accessibility is important because it breaks down barriers for people experiencing vision, cognition or motor function challenges. When we design digital tools and content with these experiences in mind, or when we make our digital tools more compatible with assistive technologies (screen readers, magnifiers, alternative keyboards, e.g.), we can improve accessibility for everyone.
Asana has made a public commitment to accessibility, and I’d love to know about what the roadmap towards WCAG 2.1 AA Guidelines looks like – are we 6 months away, or 5 years away from that goal? What aspects of accessibility will be tackled first, and what will take more time?
I’d also love to hear from anyone with use cases to share about how they made Asana more accessible. Are there features you use, or avoid, to make the tool more accessible to more people?
2 Likes
Hi,
I worked on a document to help people with ADHD use Asana, does this apply as accessibility?
Hi Bastien,
Thanks for sharing this guidance. Yes! accessibility includes cognitive accessibility - people with learning disabilities, developmental disabilities and the like.
The WCAG entry on cognitive accessibility is pretty informative - IMO the heart of it is this:
There are many things that designers and developers can do to:
- avoid accessibility barriers that exclude people from using their products
- optimize the user experience of people with cognitive and learning disabilities
1 Like
Hi Cara,
Have you had any progress on this? I am part of an institution-level push for digital accessibility, and am also looking at Asana as a potential project management solution. Asana’s statement regarding accessibility leaves much to be desired. I’m just wondering if you have been able to use Asana in a way that is digitally accessible, even WCAG compliant.
1 Like
Hi Emmanuel,
I’m still trying to gather information about this. I’ll be honest – it hasn’t been easy to come by. Where I work, we’re contemplating doing our own internal assessment of Asana’s accessibility from a user perspective. At a minimum, we want to identify best practices that maximize accessibility, and maybe even find ways for how Asana could make improvements that would benefit all users.
Let’s stay in touch so that we can compare notes and/or support each other!
Cara
Please reach out to me. We are a diverse team with staff with cross disability’s and are looking for resources for them to navigate and access Asana and the content. Our most critical priority is for a staff member who is visually disabled and requires a screen reader full time for her role.
LNaillon@LINCIdaho.org
Looking forward to connecting and thank you for your work in this critical area. Cheers!
I used to work for a nonprofit with 76% of our staff having some kind of disability. A great many of them had varying visual abilities. Each one had a different preference for what would work best for them in our technology in the office, some using screen readers, other screen magnifiers, etc. I would HIGHLY suggest that if you are doing an internal assessment, it is not completed by people without disabilities. The end users should be the ones to give you the best feedback. There are agencies out there that do nothing but give feedback and recommendations on compliance and versatility of a product, and it is done by people with disabilities. AccessiBE is one example of this. Anyway, please consider this in your team’s review. I have had grant writers on my previous teams who had low vision, and having a project management software like Asana would have been wonderful, but only if it would have worked cohesively with various types of magnification or interactivity with low-vision software that is installed for reading and magnifying screens.