AccessibleWebBot is a bot in the accessibility checkers category, operated by Accessible Web.
Accessible Web Bot crawls customer websites to discover pages and monitor for accessibility violations on regular basis. Crawls are initiated for Accessible Web's "Page Monitoring" SaaS product.
Accessibility checkers scan pages for WCAG issues on behalf of site owners and auditors. Allow the checkers you run and keep them out of analytics.
Sample user agent strings sent by AccessibleWebBot:
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; AccessibleWebBot/1.0; +https://accessibleweb.com/bot/) HeadlessChrome/81.0.4044.0 Safari/537.36Mozilla/5.0 (compatible; AccessibleWebBot/1.0; +https://accessibleweb.com/bot/)Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
We have not confirmed whether AccessibleWebBot follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: AccessibleWebBot Disallow: /
User-agent: AccessibleWebBot Disallow: /private/ Disallow: /search
User-agent: AccessibleWebBot Allow: /blog/ Disallow: /
User-agent: AccessibleWebBot Allow: / User-agent: * Disallow: /
User-agent: AccessibleWebBot group, AccessibleWebBot ignores your User-agent: * rules, so repeat any that should still apply.AccessibleWebBot from AccessibleWebBot's user agent; check Accessible Web's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow AccessibleWebBot if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersAccessibleWebBot is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow AccessibleWebBot only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf AccessibleWebBot is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows AccessibleWebBot by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
AccessibleWebBot is a bot in the accessibility checkers category, operated by Accessible Web. Accessible Web Bot crawls customer websites to discover pages and monitor for accessibility violations on regular basis. Crawls are initiated for Accessible Web's "Page Monitoring" SaaS product.
We have not confirmed whether AccessibleWebBot follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: AccessibleWebBot" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "AccessibleWebBot" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so AccessibleWebBot may not follow it, and anyone can send AccessibleWebBot's user agent, so a fake AccessibleWebBot ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Accessibility checkers scan pages for WCAG issues on behalf of site owners and auditors. Allow the checkers you run and keep them out of analytics.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.