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 have a scanning frequency that you prefer. This can be daily, weekly, monthly, quarterly, or “Dont scan”. All websites have have a default scanning frequency that you can change to set how new pages will be monitored by default. You can then override this setting on individual pages should you want to do this.

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 you see and “X” next to the page in in the page monitoring tab. 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.

  • Why am I still not seeing pages from my website show in Console?

    If you are not seeing any pages within 24 hours after adding your sitemap to your Website Settings, then there may be a problem scanning your sitemap. Make sure that the sitemap you have specified is accessible to all users (ie. not behind any authentication), and that it contains valid sitemap xml. If you have verified those items, then your site may be blocking our bot. Make sure you don’t have any entries in your robots.txt file that would block our bot from reaching your sitemap. You can learn more about our bot here.

  • Why aren’t pages from my website showing up in Console?

    Our bot currently scans sites for new pages twice a day, this is subject to change, but may be the reason you aren’t seeing the page yet. If the page still isn’t showing up after 24 hours, make sure that the page is present in the sitemap that you have specified in your Website Settings.

  • What is “Active Scanning Job” and how does Accessible Web Console schedule scanning jobs?

    “Active Scanning Job” will show the current, automatically scheduled scanning job being processed. Accessible Web Console will periodically check your website for pages that need to be scanned based on the what you have specified as their preferred scanning frequency, and when they were last scanned. When it finds one, it will group it with other pages that are also due (or close to due) and scan them together in a “scanning job”. You can expect new pages to be scanned (or at least scheduled in a scanning job) within an hour of them being detected. If you manually request a single page to be scanned, you can expect the scan to complete much quicker than this, likely within 5 minutes.

  • 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.

  • 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.