Troubleshooting
Guidance for resolving problems you may encounter when using Axe Developer Hub
Opening a Project Shows "No Scan Data Available"
If you have already run accessibility scans and are expecting to see results, you should verify the project configuration.
Verify Your API Key
Your personal API Key should be compatible with your project type. For projects integrating Axe Watcher, Web APIs, or CLI, you must use an Axe Developer Hub API key. For mobile projects, you must use an Axe DevTools Mobile API key. To create an API Key you need to have an active license for Axe Developer Hub and/or Axe DevTools Mobile. Once you have access, visit API Keys to add a new key.
- Click on the + ADD NEW API KEY button, and you will see a pop-up window like the one pictured below:
2. Select Axe Developer Hub or Axe DevTools Mobile under the Product drop down.
3. Give the API Key a Name.
4. Click Save.
After a few seconds, the updated Manage API Keys page will be displayed with as well as a message that the API Key was successfully added.
In the Actions column for your API keys, click to copy an API key to the clipboard. You should then see a message that the API key was successfully copied.
When you setset up your project, you may have copied and pasted code into your end-to-end tests. Review this code and ensure that you replaced API_KEY with the corresponding API Key
Verify Your Project ID
To find your Project ID, navigate to the Installation Instructions from the Projects page. Open the Settings dropdown for your project and select Configure Project. You'll see the Project ID, which you can click and copy to the clipboard. Review the code you copied and pasted in your end-to-end tests during project setup and ensure that you replaced all instances of PROJECT_ID with the corresponding Project ID.
Verify Scan Output Does Not Show Errors
In the window running your test, you may have errors that prevented the results from being sent to Axe Developer Hub. Carefully review these errors and resolve them.
Verify Test Completed Successfully
If your test is still running, your results may not have been sent to Developer Hub yet. Wait until your test finishes successfully and then refresh the page to see your results.
Not Seeing Results for All Scans
If you scan multiple times on the same commit (same commit SHA), results can be "overwritten" to only show the latest. When Git data is being used, you must create a new commit in order to see new scans. If you do not want to create a new commit every time you run the test, the workaround is to use Gitless testing instead. To do this, you have a couple of options:
- Delete the Git folder in the repository where your end-to-end tests are located.
- If your project integrates with Axe Watcher, use our APIs to turn off Git data collection.
As a best practice, you should run the test suite each time a new commit is created.
Git Data Doesn't Correspond to Code
If end-to-end tests are being run in a repository separate from the code you are testing, the Git data that is displayed will be for the test, not the code you are testing. If this causes confusion, our recommended workaround is to use Gitless testing instead. To do this, you have a couple of options:
- Delete the Git folder in the repository where your end-to-end tests are located.
- If your project integrates with Axe Watcher, use our APIs to turn off Git data collection.
As a best practice, we recommend that you keep the end-to-end tests in the same repository as the code you are testing.
Help
Visit support.deque.com to access knowledge base articles, Deque's SaaS product's status reports, and other product support. If you can't resolve your problem, please email us so we can help.