/ Free tool

Three regulations, one look at where you stand

Accessibility, the AI Act and privacy all attach to the same page. One scan reads all three: the accessibility score, whether an AI chatbot is disclosed, and which trackers fire before consent. It hands you a single posture with the worst of the three up top.

/ What this checks

What the posture scan reads on your page, and what its three verdicts mean.

Our server requests the address you enter with a plain HTTP GET, under a user agent that names itself as a scanner, and reads the HTML that comes back. It does not open the page in a browser or run its scripts. On that source it runs 13 accessibility checks, among them page language, title, heading order, image alt attributes, form labels, link text and viewport settings. It compares every src and href with lists of known AI chat widgets, consent platforms and tracking hosts, and it searches the visible text and naming attributes for AI disclosure phrases in English, German and Polish.

Accessibility reads Action needed when the score is below 70 or any critical finding exists (an image with no alt attribute, a form field with no label), Review below 90 and Clear otherwise. AI Act reads Action needed when a chat widget is found and no disclosure phrase is, Review when both are found, Clear when no widget is. Privacy reads Action needed when a tracker is named and no consent platform is, Review when both are, Clear when no tracker is named. The overall verdict is simply the worst of the three, so one red row turns the whole result red.

A source read cannot see colour contrast, focus order or anything a script adds after load, so a tracker injected by a tag manager or a chat widget loaded late is missed. It cannot tell whether trackers wait for consent: that takes a real browser session. A disclosure shown only inside the chat window is not found. Read Clear as nothing found in the source, and have a rendered audit settle the rest. An email, if added, is saved with the page address and the verdicts.

What does Article 50 of the EU AI Act require for chatbots?
Article 50 sets transparency duties. A provider of an AI system that interacts directly with people must design it so that those people are informed they are dealing with an AI system, unless this is obvious to a reasonably well-informed and observant person in the circumstances. The same article covers the marking of AI-generated content and the disclosure of deepfakes. It does not ban chatbots; it requires that their nature is made clear.
Do I need consent before loading Google Analytics in the EU?
Under the ePrivacy rules as applied across the EU, storing or reading information on a visitor's device needs prior consent unless it is strictly necessary for the service the visitor asked for. Analytics cookies are generally not treated as strictly necessary, so a script that sets them should not run before the visitor agrees. Some national regulators exempt narrowly configured audience measurement, so the detail depends on the country.
What is the European Accessibility Act and who has to comply?
The European Accessibility Act is Directive (EU) 2019/882. It requires certain products and services sold to consumers in the EU to be accessible, including online shops, consumer banking, e-books and passenger transport ticketing, and it has applied since 28 June 2025. Microenterprises that provide services are exempt. For websites, the harmonised standard EN 301 549 refers to WCAG 2.1 level AA.
Next

When one check is not the whole job.

Behind on one of them? Each maps to a door: prove where you stand, fix it, keep it proven.