We believe embedding accessibility standards and testing into the development process is the most efficient approach to creating an accessible website. Many of DubBot's clients, agencies in particular, use automated and manual testing consistently to expose and remediate accessibility issues before moving their website into production.
With DubBot, you can configure automated accessibility testing for your web development site, in most cases, even if it's behind a login. Doing so will help you and your team ensure accessibility compliance before your website goes live.
For more information, see the Help Center article "Crawling a Development Site."
Robots.txt - Do I Need to Update My Settings?
Depending on how the robots.txt file is configured on your development server, DubBot might be prevented from crawling your site. For DubBot to access your development site, you might need to ignore robots.txt. To do this, navigate to "Settings" and then to the "Advanced" tab in the DubBot app. Uncheck "Obey robots.txt."
If the DubBot crawler still can not access your development site, it's possible that our crawler is being blocked. We maintain a static IP of 34.213.65.175, which your server admin can add.
Many of the support tickets that we receive are solved simply by allow-listing our crawler and double-checking your robots.txt settings.
More information on robots.txt settings can be found in our Help Center.
Crawling Behind Authentication
If your development site requires authentication, there is a likelihood that DubBot could test the site. It should be noted that this feature is not enabled by default, so you might need to contact DubBot’s support team. If it is enabled, information on authentication and proper settings in DubBot is available in the Help Center article "Crawling Behind Log in."
If you have questions, please get in touch with our DubBot Support team via email at help@dubbot.com or via the blue chat bubble in the lower right corner of your screen.
Resources
- Start with Accessibility - W3C
