You are probably here because Strickle fetched your home page.

Here is exactly what it did, what it did not do, and how to stop it. If anything below does not match what you saw in your logs, please tell us.

User agent: strickle/0.5.0 (+https://strickleworks.com; douglas@kordloom.com)
What it requests: Your robots.txt, then your home page. Nothing else.
How often: At most once per night, and at most one request per second.
robots.txt: Honored, including Crawl-delay. If your robots.txt disallows us, we record that we were not permitted to look and publish nothing about your site.
Never: No forms, no logins, no search boxes, no personal data, no attempt to work around a block or a challenge page.

Turning it off

Add this to your robots.txt and the next run will skip you:

User-agent: strickle
Disallow: /

That takes effect within 24 hours and needs no confirmation from us. If you would rather we stopped immediately, or you want the traffic explained to someone in your organization, email douglas@kordloom.com and a person will answer.

What Strickle is

Strickle looks at public sector home pages and records which WCAG 2.1 checks the delivered markup fails. It keeps every look, dated, alongside the exact bytes it was judging, so any finding can be re-derived from its own evidence years later.

The record is the point. A single scan is an audit, and an audit goes stale. A scan repeated on a schedule and written down becomes a history, and a history cannot be reconstructed after the fact. That is the part nobody can catch up on later.

Findings are deliberately conservative. Every check fires only on an unambiguous failure in the markup, because a finding shown to a public body may be forwarded to its counsel, and a false positive costs far more than a missed issue. Checks that need a rendered page are reported as not examined, never as passed.

Why now

The Department of Justice's rule under Title II of the Americans with Disabilities Act sets WCAG 2.1 Level AA as the standard for state and local government websites, with compliance dates already fixed:

26 Apr 2027 Public entities serving a population of 50,000 or more.

26 Apr 2028 Smaller public entities and special district governments.

The obligation does not transfer to a web vendor. It stays with the public entity, which is why a dated, independent record of what a site actually looked like is worth keeping.