The method is published in full: what a scan does step by step, and the limits of each source it reads.
Reads robots.txt first and never asks for a page that a group naming ArablyzerBot disallows: the scan stops, and the report says so, with the rule and its line. Before it follows a redirect to another site, it reads that site's robots.txt too. A User-agent: * group alone does not stop a scan, since a scan someone asks for is a visit, not a crawl, and a robots.txt that cannot be read does not stop it either. Every scan reads robots.txt afresh.
Fetches the page through a single egress proxy that refuses private addresses and the server's own, and follows up to ten redirects.
Reads the page's HTML as it arrived, before any script: title, description, language, direction, links, structured data and forms.
Asks DNS for the mail records when its rules need them: the TXT records of the page's organizational domain and of its _dmarc name, and nothing else, within ten seconds at most. On the hosted service the two questions go as DNS over HTTPS (RFC 8484) to Cloudflare's resolver (https://cloudflare-dns.com/dns-query), or to the resolver the service is configured with, through the same egress proxy as the rest of its traffic: the domain's name goes to that resolver, and nothing else of the page. A scan that runs on a machine without an egress proxy, such as the command-line tool, asks that machine's DNS servers. When a scan has no way to ask DNS, it leaves those rules out, and the report says so.
Asks for the page's links to its own site when the broken-link rule needs them: it counts 1,000 links at most on a page, and asks for the first 50 links to the page's own origin, four at a time, within 20 seconds in all, and each request within 10 seconds (a link can take two requests), that robots.txt does not keep from ArablyzerBot, by a group that names it or by the User-agent: * group, since the links are not the visit someone asked for, each with a HEAD request, then a GET where it answers an error or the connection fails, through the same egress proxy, following no redirect and reading no content.
Renders the page in browsers when asked: Chromium and Firefox, and WebKit on servers with an isolated network. In each engine it measures Arabic text, direction, fonts and form fields, runs a curated set of axe-core's accessibility rules, and reads the stylesheets and fonts the browser loaded. No browser sends anything the page asks it to send: it refuses every request that is not GET or HEAD, wherever it goes, and closes every WebSocket before it opens, so no form, sendBeacon or POST request goes out; it contacts at most 50 different hosts; and the report says what was refused.
Runs the rules : each is a fixed function that reads what was collected and fetches nothing, so the same page gives the same result every time.