Since August 2, 2026, Europe Requires Your Chatbot to Say It Is AI

On August 2, 2026, Article 50 of the European AI Act started to apply. It is the part of the law most product teams will actually touch, because it is about the moment a person meets an AI system. If your product talks to people through a model, and some of those people are in Europe, this article is now your problem.

Most of the coverage this summer was about what got delayed. The Digital Omnibus on AI entered into force on July 27, and the European Commission's own page on the AI Act lists what moved: the high risk rules for areas like hiring and education now start on December 2, 2027, and the rules for AI inside regulated products start in August 2028. A lot of people read that as "the AI Act is on hold." It is not. The transparency rules kept their date.

I read Article 50 as a designer, and what struck me is how little of it is legal abstraction. Most of it is an interface spec.

What the article asks for

The full text is on the Commission's AI Act Service Desk. Stripped down, there are four obligations that matter for product work.

First, providers of AI systems meant to interact directly with people have to design them so that those people are informed they are dealing with an AI system. The exception is when it is obvious to a reasonably well informed person from the context. That word "design" is in the law. The obligation sits with whoever builds the thing.

Second, systems that generate synthetic audio, images, video or text have to mark their output in a machine readable format, so it can be detected as artificially generated. This applies as far as it is technically feasible, and there are exceptions for assistive editing and for tools that do not substantially change what the user gave them.

Third, deployers that publish deepfakes have to disclose them. AI generated text published to inform the public on matters of public interest also has to be disclosed, unless a human reviewed it and someone holds editorial responsibility.

Fourth, and this is the line I would print and tape to the wall, the information has to be given in a clear and distinguishable manner, at the latest at the time of the first interaction or exposure, and it has to meet applicable accessibility requirements.

You could hand that sentence to a designer as acceptance criteria and they would know exactly what to do with it.

Who it reaches

Article 2 sets the scope, and it is wide. It covers providers that place AI systems on the EU market even if they are based outside the EU, and providers and deployers in third countries when the output of the system is used in the Union. I build products from Tokyo. If someone in Lisbon downloads one of my apps and talks to it, the output is used in the Union.

The penalties are in Article 99. Breaching the Article 50 obligations can cost up to EUR 15 million or 3% of total worldwide annual turnover, whichever is higher. For small and medium companies, including startups, the cap is whichever of the two is lower. That is still not a number a small team wants to meet.

There is one transitional break. Under Article 111, as amended, providers whose generative systems were already on the market before August 2, 2026 have until December 2, 2026 to comply with the machine readable marking rule. The disclosure to the person in front of the screen has no such grace period in the text.

The disclosure most products ship today

Look at how AI features are labeled in products right now. A small sparkle icon. A gray line of legal copy under the input box. A badge that says "Beta." A sentence in the terms of service that nobody opens.

From a distance these look like disclosure. Up close, most of them fail the test in the law. A sparkle icon tells you there is something new in the product. It does not tell you that the thing answering you is a model. Gray microcopy under the input is technically present, but it is designed to be skipped, and "distinguishable" is a hard word to satisfy with text that was styled to disappear. A sentence in the terms is not given at the first interaction, because nobody reads the terms at the first interaction.

The hardest case is voice. I design products where people talk to a model and it talks back, and there is no gray line to hide anything in. The first interaction is a sound. If the disclosure is going to happen at the first interaction, it has to happen in the conversation itself, or on the screen the person sees right before they start talking. That is a design decision with a real cost, because every second of preamble before the first answer makes the product feel slower.

How I would design it

I would start from that sentence in paragraph 5 and treat each part of it like any other requirement.

Clear means plain language. "You are talking to an AI assistant" works. "Powered by advanced intelligence" does not, because a reasonable person can read it and still believe a human is on the other end.

Distinguishable means it cannot look like the rest of the chrome. Give it its own line, its own weight, and contrast that passes. If your design system has a pattern for important notices, use that one, and do not invent a quieter version just for this.

First interaction means before or at the first message, every time a new person arrives. Onboarding screens are fine, but think about the person who enters through a shared link or a widget on a support page and never sees onboarding. The persistent place to put it is the conversation surface itself, near the name of the assistant.

Accessible means the disclosure has to survive a screen reader, zoom, and a voice interface. If it is only conveyed by an icon, it is not there for someone who cannot see the icon. If your assistant speaks, the spoken version counts.

For generated media, the machine readable marking is an engineering job, and it belongs in the export pipeline, not in the UI. The design job is the human readable part for deepfakes and published text, and the law lets you keep that light for evidently artistic or satirical work so it does not ruin the piece.

Why I think this is a good rule

I expected to be annoyed by this article. I am not.

Every AI product I have worked on got better when people knew what they were talking to. They ask better questions, and they check the answer when it matters instead of trusting it like a colleague. The products that try to blur the line usually do it because the honest version tested worse on some engagement number, and that is a short term trade that tends to come back as a trust problem later.

The European version of this rule has teeth, which is unusual. Japan took the opposite approach with its own AI law, which has no penalties at all, and I wrote about why that makes the interface the compliance layer there too. Both roads end at the same screen. Someone has to decide what the person sees at the first interaction, and in most companies that person is a designer who was never told it is now a legal requirement.

If you ship an AI feature that reaches Europe, open it as a new user today and write down the first thing that tells you a model is answering. If you cannot find it, or it took you more than a few seconds, that is your August 2 work, and it is already late.

This is a product reading of the regulation, not legal advice. For your own case, read the article text and talk to someone who practices EU law.