I've used AQA on several projects and the team has been incredibly responsive to requests and feedback. They improve the tool regularly and take users' feedback to heart. Compared to other similar platforms they are reasonably priced and provide many in-depth reporting options for stakeholders through development teams. Highly recommend.

AQA is an easy-to-learn tool that allows for quicker auditing, manual testing, and defect creation. It integrates with JIRA easily and now has the ability to test emails and documents. Using AQA has saved a considerable amount of time compared to documenting defects on a spreadsheet and creating defects manually. It has been a game-changer for the projects I have worked on.

Integrating with some platforms who don't use traditional code can be tricky. The team has been great about finding work-arounds. The downfall is we have needed the AQA tech team to customize the platform for us in order to adequately test the platform our client is using.

Working with UsableNet, we're now able to measure and track the accessibility of our web products, and for the first time ever, report an accessibility score on our Engineering Scorecard, alongside other important metrics like performance and security. The UsableNet team are also great to work with, always responding to queries quickly and in a very helpful way.

AQA allows us to carry out accessibility audits of our web platforms pretty painlessly. I love how it steps you through the manual checks and also shows you visually exactly where errors appear on the page. Having the 'auto only' options is great too. The reporting options are excellent, particularly the one for stakeholders showing an overall accessibility score and a summary of issues, and the one for dev teams with links into the tool for every issue. It's also really helpful to see the issues shown on a complexity/severity chart – super useful.

There are some elements we feel could be improved, which the team at UsableNet are always interested in hearing about and will work on improvements if they can. It would also be great if we could run our own tests on native apps, but I know this is a little more tricky!

It is potentially critical to our organization becoming ADA compliant and avoiding any lawsuits

It is not the most user-friendly - the explanation of certain things which are reported is not always clear and sometimes can be downright confusing and frustrating. Additional clarity on certain elements would go a long way towards improving users' satisfaction with the software.

Still ramping up - but I am excited to use this tool to automate processes and bring all teams into compliance using a single tool to report and manage accessibility.

We were able to deploy an internal instance to test products on our internal servers. We can also use the browser extension for quick tests.

We had some issues deploying the internal instance - but the team is very responsive and helpful.

Overall, good product but some improvements should be done. I like that it helped us greatly to improve accessibility on our site and the team is helpful when questions arise.

- Very clear difference between automatic issues and issues that can be manually determined to be fixed or not. - Liked the rating of issues from easy to hard fix and their priority/impact. - Having sessions with the AQA team was valuable when we had questions/concerns. The team is very nice and helpful, they try their best to give personalized advice, however, beware that a lot depends on the quality of your website's code and your resources to fix it. - I loved the report exporting feature and that I was able to download the spreadsheet with all issues on all pages that were tested. I used the spreadsheet way more than the access to projects/tests via AQA itself. Spreadsheets are more intuitive.

- There has been a lot of confusion between "tests" and "audits" for our team. We still do not see much difference between the two and do not understand why there has to be both when they do look identical and offer identical information upon the analysis. In audits, it's even harder to find access to the issues Review page. I also don't understand why I can run a new test but cannot run a new audit. There are no quick tooltips or anything like that to explain the feature. - I think there has to be a lot of work done across the platform in terms of wording. I spent a lot of time understanding how to download an excel spreadsheet with the test results. It says "run the report" (or something of this sort). Why not say "download the report" instead? It's more straightforward. - There is no way to leave a comment on the platform to the commenter from the AQA team directly. I used Jira to communicate with the AQA team and ask questions there, which does take additional time of yours, however, I like how I could share screenshots and format text there for more clarity. - There's a chat feature that my team never used. I think unless there's a possibility to chat with AQA's team via this chat, it is not really helpful. - In this exact review survey, they are asking to rate some of the features I've never even seen or heard of. I tried googling them and no results. It's hard to understand what they are talking about if there's no consistency in wording across all touchpoints