Crawling Tests Overview
AMP allows users to create automated tests that crawl a domain from a specified Start URL and test all pages encountered by the crawl. When automated testing is performed in this manner, the results are saved to an AMP report that is created when the test is run. AMP Tests are saved so the same accessibility audit configuration can be run multiple times in order to set up repeatable audits. This allows users to enter the desired Test setting once, and then have AMP conduct the same audit on a regular basis. Each time the AMP test is run, your team will receive a new report that details your overall level of compliance, top violations, and other critical pieces of information to support your remediation efforts. This is also a great way to track your progress over time, as you’ll begin to develop a data set that highlights potential training gaps and/or bugs that continue to be released into production
Tests are then associated with an Asset to ensure that testing efforts remain organized and easily navigable by all AMP users. All reports generated from a Test are stored within the same Asset. All Assets which a user has access to are located within the Assets area of the parent organization.
Creating a Crawling Test
Crawling Test Limitations
Crawling tests and the services that drive them are components of AMP and are initiated from the AMP server. As such any pages that you wish to crawl must be available to the server. This typically means that any non-publically facing pages will not testable via a crawl and should be tested via Access Assistant.
Intranet sites can be crawled if our Crawl Services can be whitelisted by the firewall: Firewall and Filter Exclusions
Content behind authentication may be able to be crawled by Recording a Macro, using Access Assistant, of the login for AMPs Crawl services to playback:
*Note that Multifactor authentication, Single Sign On authentication, and authentication pathways that route through a portal will not work with the Macro feature.