Overview
AccessibeBot identifies accessiBe accessFlow accessibility audit requests when configured with a crawler-specific user-agent suffix.
The operator documents how accessFlow customers can set an audit user agent containing the AccessibeBot token and a customer-specific secret. This is an audit traffic identity, not a general web indexer.
Identification: AccessibeBot.
Operator documentation: https://support.accessibe.com/hc/en-us/articles/32633352499474-How-to-fix-a-failed-accessFlow-audit-blocked-by-Cloudflare.
Identity
- User-Agent Pattern
-
AccessibeBot - Identity Type
- Officially documented
- Evidence Method
- operator documentation; user-agent alone is untrusted
Classification
- Type
- Security
- Kind
- Accessibility audit fetcher
- Family
- accessiBe
- Purpose
- Accessibility compliance audits
Behavior and handling
- Common Use
- accessibility compliance audits
- Detection Notes
- Match the distinctive AccessibeBot token. Operator example uses AccessibeBot/1.0/{userSecret}, where the suffix is customer-specific. No universal fixed full user agent or robots.txt behavior is documented. Never copy a customer secret.
- Respects robots.txt
- Unknown
- Spoofing Risk
- The AccessibeBot User-Agent token can be impersonated; confirm provenance before trusting it.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# No confirmed universal robots.txt control; use validated access controls as needed.
Relationships
- Operator
- accessiBe Checked 2026-10-22
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.