- From: Fabien Gandon <fabien.gandon@inria.fr>
- Date: Wed, 28 Jan 2026 14:02:08 +0100 (CET)
- To: WebAI Interest Group at W3C <public-webai@w3.org>
- Message-ID: <2146132157.6574861.1769605328178.JavaMail.zimbra@inria.fr>
Hello David, Thanks for sharing these pointers on the list. I found the discussion on [ https://github.com/WICG/proposals/issues/261 | issue 261 ] interesting. I wondered if discussions also started on the potential incentives (beyond EU regulation) for content providers, publishers, etc. to adopt and include such disclosure attribute and its granularity? Best regards, Fabien Gandon, [ https://team.inria.fr/wimmics/ | Wimmics ] (Inria, Université Côte d’Azur, CNRS, I3S, France) [ https://twitter.com/fabien_gandon | @fabien_gandon ] - [ http://fabien.info/ | http://fabien.info ] > De: "David E. Weekly" <dweekly@gmail.com> > À: "WebAI Interest Group at W3C" <public-webai@w3.org> > Envoyé: Lundi 26 Janvier 2026 23:13:43 > Objet: Proposal: Element-level AI content disclosure in HTML > Hi all, > I've been working on a proposal for standardizing how web authors disclose AI > involvement in HTML content — not at the page level (which whatwg/html#9479 > covers) or the HTTP level (which the IETF AI-Disclosure header covers), but at > the element level, so a page with a human-written article and an AI-generated > sidebar can label each section appropriately. > The proposal adds an `ai-disclosure` attribute to any HTML element with four > values: `none`, `ai-assisted`, `ai-generated`, and `autonomous`, aligned with > the IETF header and IPTC Digital Source Type vocabulary. It's designed to > complement C2PA rather than compete with it — voluntary declaration vs. > cryptographic verification. > Some context on where things stand: > - Explainer: [ https://github.com/dweekly/ai-content-disclosure | > https://github.com/dweekly/ai-content-disclosure ] > - WICG proposal: [ https://github.com/WICG/proposals/issues/261 | > https://github.com/WICG/proposals/issues/261 ] > - ChromeStatus: [ https://chromestatus.com/feature/5078123181899776 | > https://chromestatus.com/feature/5078123181899776 ] > - Mozilla standards position: [ > https://github.com/mozilla/standards-positions/issues/1344 | > https://github.com/mozilla/standards-positions/issues/1344 ] > - WebKit standards position: [ > https://github.com/WebKit/standards-positions/issues/605 | > https://github.com/WebKit/standards-positions/issues/605 ] > One of the motivations is the EU AI Act Article 50 requirement for > machine-readable marking of AI-generated text (effective August 2026). Happy to > present at a meeting if that would be useful. > - David
Received on Wednesday, 28 January 2026 13:02:13 UTC