Check a public website
The form below starts an automated check of a public website and returns a link to its status and report. The request uses the English interface and report presentation when the service supports it.

Pilot operation
The request interface is in English. Reports and generated specifications may be supplied in Russian; result links indicate their language.
The service works in pilot mode. Computing capacity is limited: no more than a limited number of checks run at the same time, so new requests go into a queue. One check takes from several to dozens of minutes depending on the site. The result is not immediate: after a request is sent, a page with the status opens, and when the check is finished the page shows a link to the report.
Queue state
Checking the queue state...
Send a request
Request status
Loading the request status...
What is checked
- Automatic checks of WCAG 2.2 levels A and AA follow the shared technical methodology of the project. The international overview compares national and regional sources; the automatic result does not determine legal compliance.
- A sample of up to 15 pages of the site, not the whole site.
- The site address and the technical data of the request are stored for 30 days together with the report and are deleted afterwards. The address of the report is known only to the holder of the link.
- The notification about the ready report in Telegram is optional: the bot knows only the chat number linked to a specific request and removes that link right after the notification is sent.
- The site must be public: closed, internal and local addresses are not accepted.
- The check respects the rules of robots.txt of the site being checked.
The automatic check does not confirm full conformance: it proves the defects it has found and describes honestly which part of the criteria is checked automatically and which part needs a manual check (see the automatisation map).
What the check covers
The service checks a bounded sample of pages and states that it can reach without signing in. It respects technical access limits, including robots rules and responses from the target site. A report describes the sample, successful checks, detected problems and checks that could not be completed.
What it does not prove
The result does not certify the whole website. It does not replace keyboard testing, assistive technology testing, document review or sessions with disabled users. Dynamic states, private areas, payments and other critical processes may require a separate plan.
Before submitting
Submit only a public address that you are permitted to check. Do not place passwords, personal data or confidential tokens in the address. Review the report before using it for decisions, and confirm important findings manually with the evaluation method.
Data handling
The service needs the submitted address and technical evidence required to produce the report. Keep the returned links according to your organisation's retention rules and avoid sharing a report that contains information you are not authorised to disclose.