Automated Accessibility Scanning

You can request automated accessibility scanning of pages on your website from within the Accessible Web Console. 

To do this, you first need to make sure that all the pages you want scanned are added to your Console. You can do this by navigating to the Page Monitoring tab and adding the pages there. You can also automatically import pages from your website if you have many pages to add, and would like new pages to be automatically added in the future.

Once all the pages you wish to scan have been added to your Console, you can make sure they are added to a Scan Group that scans on your preferred scanning frequency. All websites will have a Default Scan Group. You can edit and create many scan groups with different scanning frequencies.

Within the Console Settings tab, you can adjust the WCAG version & level that the scanner checks. We recommend WCAG 2.1, Level AA.

Remember to Adjust Your Analytics Account

If you have analytics on your website, like Google Analytics, remember to filter out our Accessibility Bot from you data. Otherwise you will see it as real traffic on your site. Learn how to filter out the Accessibility Bot from analytics.

Viewing Scanning Results

The scan results are attached directly to the pages within your Console. You can navigate to a page through the Page Monitoring tab.

Scanning Errors

If our scanner encounters an error, it may decide to remove the pages eligibility for automatic scanning. You will know that this is the case if a page is a part of a scan group, and you see a notice stating the page is no longer eligible for automatic scanning. An error that causes this may be one of the following.

  • Invalid status code. This happens if the page returns a 404, or any other status code our scanner deems unfit for future scanning.
  • Aborted, possibly due to unsupported content. Something about the content type of the page didn’t allow for proper scanning. This will often happen if you try to scan a PDF, or CSV, for example.
  • Too many redirects, which is an error that occurs if a redirect loop is detected.
  • Domain not resolved. If your domain is not properly resolved to an IP address.
  • Different hostname. To make sure that we aren’t scanning external websites, we verify that the hostname of your website is the same page we land on. This means that we only scan pages that live on your website. It’s important to know that the hostname www.example.com, is considered a different website than example.com in this comparison. So make sure that your primary domain is set up properly.

Troubleshooting & Frequently Asked Questions

Have questions you aren’t seeing the answers to? Get in contact with us.

  • Is there a way to manually trigger a scan of a page?

    Yes! Navigate to the page within your Console account, and click the Scan Page button.

  • What rules are being checked during the accessibility scan?

    Accessible Web uses Axe Core to perform accessibility scans of the pages you request. We run the scan on your page and check for violations of WCAG 2.1 AA by default. If you would like to change the rules that we are checking for, you can adjust these settings in the Console Settings tab of you website.