Lets custom element authors use ElementInternals to set a custom element's default accessibility role, states, and properties, much like the default accessibility semantics for native elements.


There is currently no way for a custom element author to set default custom element accessibility semantics for a custom element. They can use AOM and modify ARIA attributes on the custom element directly, however these are user-visible and user-modifiable. An example of why this is bad: if the default attributes are modified by the user, and later on they remove the attribute, the default value would not be restored.




Specification link

Unknown standards status - check spec link for status

Status in Chromium


Enabled by default (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Positive
  • No signal
  • No signals


Intent to Prototype url

Intent to Prototype thread

Last updated on 2021-12-13