The AccessiLume scanner
If AccessiLume shows up in your server logs, it came from our accessibility scanner. It visits a page only because someone using AccessiLume asked to check it for accessibility barriers.
How to recognise it
Every request the scanner makes sends this User-Agent:
AccessiLume/1.0 (+https://www.accessilume.com/scanner; formerly AccessiShield)AccessiLume was called AccessiShield until September 2026. The old name stays in the User-Agent so allowlists written for it keep matching.
What it fetches
A scan opens a page in a headless browser, so it loads the resources that page requests, the same way a visitor's browser would.
Single-page scans and monitoring rescans fetch only the specific address a user chose. A site crawl discovers pages on its own: it reads your robots.txt first, skips every page it disallows, and waits between pages when robots.txt sets a Crawl-delay (up to 10 seconds).
Controlling crawls with robots.txt
Crawls follow the group written for AccessiLume. If there is none, they follow a group written for AccessiShield, and otherwise the * group. To keep crawls off your whole site:
User-agent: AccessiLume
Disallow: /Questions
If the scanner causes a problem on your site, email support@accessilume.com and we will look into it.