Official-source-backed technical resource
Specify an AI identity component in a design system
Define the component's content, placement and state behavior alongside its visual design. Includes a free implementation worksheet.
Short answer
Define the component's content, placement and state behavior alongside its visual design. Make integration requirements explicit so teams do not treat it as a decorative badge.
Download the blank working record (.md)
When to use this guide
Several product teams reuse a small AI icon but place it after the interaction or omit accessible text.
This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.
Review procedure
-
Document the identity text and supported display states.
-
Specify where the component belongs relative to the first interaction.
-
Provide keyboard, screen-reader, narrow-layout and loading examples.
-
Review implementations in actual products and record deviations from the component contract.
What the example review finds
-
The icon alone has no understandable accessible name.
-
A team renders the component only after the first reply.
Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.
Fields for your working record
-
Component version
-
Content contract
-
Placement rule
-
Supported state
-
Integration review
Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.
Completion and handoff
Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.
Decision boundary
A shared component reduces inconsistency but does not establish the adequacy of each product's disclosure.
The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.
Official sources
Last reviewed: 2026-09-23. This is technical implementation information, not legal advice.