RatedWithAI

RatedWithAI

Accessibility scanner

Free tool · no signup

AI disclosure notice generator

Most AI rules that reach a normal company are not about the model. They are about what you have to tell people: that they are talking to a machine, that a system read their application, that a picture was generated. Pick what you run and where it reaches, and take the text.

Every block names its instrument and provision, says where it has to appear and when it bites, and links the primary source. Nothing to sign up for, nothing sent anywhere — it all runs in this tab.

1 · What you run
2 · Whose residents it reaches
3 · Your role

A handful of duties — the training-data summary, the machine-readable marking — sit only with whoever put the system on the market.

1 notice to publish, soonest deadline first.

You are talking to an AI

In force 2026-08-02

EU AI Act (Regulation 2024/1689) · Article 50(1)

A provider of a system that interacts with people must make sure the person knows it is an AI, unless that is obvious to a reasonably well-informed person.

Where it goes: Inside the product, before the person interacts

You are chatting with an automated assistant, not a person.

[Company] uses an AI system to answer questions here. It can be wrong. Ask for a human at any time and we will pass you to one.
Read Article 50(1) →checked 2026-09-23

Drafting aid, not legal advice. Every block names its instrument and provision, and the date we last read it, so you can check it against the primary source — and a regulator reads the text you publish, not the text we suggested.

What this covers today

  • California AB 2013 (Generative AI: Training Data Transparency)
  • California B&P Code § 17941 (B.O.T. Act)
  • California Invasion of Privacy Act (Penal Code § 631/632)
  • Colorado AI Act (SB 24-205)
  • EU AI Act (Regulation 2024/1689)
  • FTC Act § 5 / Endorsement Guides
  • Illinois AI Video Interview Act
  • Illinois HB 3773 (Human Rights Act amendment)
  • New York City Local Law 144 of 2021
  • Texas Responsible AI Governance Act (HB 149)
  • Utah AI Policy Act (SB 149, amended SB 226/332)

Not covered, deliberately: sector rules that are not disclosure duties (the FDA's device pathway, the EU's financial-services guidance), and anything that has been proposed but not enacted. If a block is missing an instrument you are subject to, the gap is real — we would rather ship nothing there than a paragraph nobody checked.

Questions

Is this legal advice?
No. It is a drafting aid. What it does that a blank page does not is name the instrument and the exact provision behind every block, and date the reading, so you or your counsel can check each one against the primary source in a few minutes rather than working out from scratch which laws even reach you. A regulator reads the text you publish, not the text we suggested.
Why does a chatbot notice differ from a bot disclosure?
Because they are three different duties with three different triggers. EU AI Act Article 50(1) applies to systems that interact with people and asks you to make the AI evident. California's B.O.T. Act only bites when a bot is used to incentivise a sale or influence a vote, and it wants a disclosure a reasonable person would notice. The CIPA line is not an AI duty at all — it is a wiretapping consent, and it exists because your chat vendor is a third party reading the conversation as it happens. A single sentence saying "I'm a bot" satisfies the first two and none of the third.
The EU marking block is not copy. Why is it in here?
Article 50(2) asks for the output to be marked in a machine-readable way — metadata, a watermark, a provenance manifest. A visible sentence under the image does not satisfy it, and that is the single most common way this obligation is missed, so the block tells you what to implement and gives you the public line to sit alongside it rather than pretending a paragraph is enough.
I picked several places and got fewer notices than I expected.
Role filters some of them. The training-data summary and the machine-readable marking sit with whoever put the system on the market, so they disappear when you say you use someone else's product. Everything that attaches to the decision you make — the hiring notices, the Colorado consumer notice, the workplace notice — stays with you either way, because buying a vendor's system does not move that duty upstream.
How current is this?
Every block carries the date it was last read against its source, and the source link sits next to it. As of now it covers 11 instruments. Dates move — the Colorado act has already been delayed once — so check the deadline on the block before you plan around it.
What does accessibility have to do with AI disclosure?
Directly, nothing, and the notice text above does not pretend otherwise. Indirectly: the page you publish these notices on is a page, and the same law that makes you disclose the system frequently makes the disclosure itself an accessibility obligation — a notice nobody using a screen reader can read is not a notice. The scan below is free and answers that part.

The page you publish these on

A notice nobody can read is not a notice

Every page crawled against WCAG 2.1 AA, with the failing element named on each one. Free, no signup, no card.

Working out which obligations apply at all, rather than what to publish? The AI obligation checker answers that one.