Show someone a small four-pointed star glowing over a button, out of context, and ask what it means. In Nielsen Norman Group’s 2024 test, 107 people did exactly that with the sparkle icon as it appears in real apps like Lyft and Plane Finder — and not one said “artificial intelligence,” according to Kate Kaplan’s research for NN/g . Since 2 August 2026, Article 50 of the EU AI Act has required that AI-generated content carry a label that is clear, visible, accessible to assistive technology, and durable enough to survive a reshare — a stamp about where an output came from, not a promise about what a feature can do. The sparkle the industry settled on was built for the second job. The law now needs the first, and nothing about the glyph was ever designed to carry it.
The sparkle was designed to sell wonder, not prove origin
The convention has a real design history, none of it aimed at compliance. Google put a sparkle on Google Docs’ Explore feature back in 2016, and by 2024 nearly 100 distinct AI sparkle variants were circulating across Google’s own products alone, appearing at a quarterly growth rate as high as 37%, according to Google’s own design research by Rose Pozos and Lennard Schmidt. The people who chose it say so directly: Zoom’s Madison Holbrook told Fast Company the icon “carries a sense of wonder and delight” and captures AI’s “almost magical quality… in a single, universally understood symbol.”
That’s the vocabulary of a feature badge, not a content label, and Nielsen Norman Group’s testing shows exactly the gap it leaves. Shown the icon alone, participants guessed favoriting, visual polish, anything but AI:
In the absence of a heart, I think the star would allow me to save items.
Kate Kaplan’s advice out of that study was to never ship the sparkle without a text label beside it — a caveat about to become load-bearing rather than optional for any team shipping to the EU.
Google’s own numbers say the icon works, with a large caveat
That reading isn’t unanimous. Google’s design team surveyed 2,000 participants across eight countries and found close to the opposite: users do recognize sparkles as signaling AI, a single sparkle communicates that effectively, and combined marks — a microphone plus a sparkle, say — perform even better, per the same Pozos and Schmidt research. Participants cared more about trusting an AI feature than about identifying which kind of AI was involved.
The sparkle the industry settled on was built to sell delight, not to prove where a piece of content came from.
The honest complication is who ran the test. Google’s product suite drove the convention in the first place, and its researchers are measuring recognition of an icon their own products spent a decade normalizing — unlike NN/g’s 2024 test, which showed the glyph stripped of any brand or context. Neither study measured whether an in-context sparkle satisfies what Article 50 actually asks: identify a specific piece of content as machine-made, not just signal that AI is somewhere nearby. Read across that gap, the case for treating today’s sparkle as compliant collapses not because either study is wrong, but because neither was built to answer that question.
Provenance needs a mark the sparkle was never built to carry
The European Commission didn’t leave designers guessing what the second mark should look like. Its free icon set, published for anyone working toward Article 50 , offers three icons — one for AI-assisted content generally, one for content fully generated by a machine, one for human work an AI has modified — each in four color variants, no attribution required. Open the set and the split is visible immediately: none of the three replaces the toolbar sparkle that announces a feature. They belong on the artifact, not the button that made it, and the Commission is explicit that downloading them “does not establish legal compliance by itself.” Its own testing found the same thing Kaplan did in 2024: “performance improved across all measures when the basic icon was accompanied by a text label.”
Vitaly Friedman’s rundown of the new guidelines for Smashing Magazine draws the same line — a barely visible icon, a footnote, a label that flashes and vanishes, none of it clears the bar — and points to IBM’s Carbon Design System AI Label as one production pattern built for durability, not delight. That’s the job a product designer or design-system maintainer shipping to EU users is now stuck holding: the sparkle already in their component library still sells a feature well, but it was never asked to survive a reshare, work with a screen reader, or say “a machine made this” about one piece of content. Every team with EU users now owes their interface two separate marks where they used to ship one, much as the same regulation already forced chatbot interfaces to stop hiding their human handoff behind friendly design instead of simply disclosing it. Building the second mark is not a restyle of the first.
The sparkle will keep doing the job it was hired for, selling a feature as something worth trying. What it can’t do, in any product it appears in, is tell a screen reader, a browser, or a regulator which pixels a machine actually made.
