Browser vendors back a new accessible component metadata standard

Tech · 5 min read

A working group made up of contributors from Chromium, WebKit, and major accessibility tool vendors published a draft specification called Accessible Component Metadata (ACM). The proposal defines a lightweight JSON-LD envelope that design systems can include with components to surface semantic role, expected behaviors, personalization hooks, and accessibility assertions (like required contrast ratio or whether a component manages focus).

ACM aims to bridge gaps between static design artifacts and runtime assistive technologies. For example, a button component could ship with metadata describing that it behaves as a toggle, needs a visible focus ring at a minimum size, and exposes an ARIA state mapping. Browser engines and AT vendors could consume ACM to optimize rendering, provide better authoring warnings, or automatically offer appropriate keyboard shortcuts to users.

Privacy and performance have been central to the discussion. The spec recommends optional metadata, compressed formats, and permissioned access so user agents only request metadata when necessary. The working group is also exploring how ACM can interoperate with existing standards like ARIA, design tokens, and localization bundles without duplicating responsibilities.

If adopted, ACM could reduce friction between design systems and platform assistive tech—shortening the feedback loop when components fail in real-world usage. The draft is open for public comment, and the working group expects prototype implementations from tool vendors later this year.