Default Accessibility Semantics for Custom Elements

[alice]

Request for Mozilla Position on an Emerging Web Specification

• Specification Title: Default Accessibility Semantics for Custom Elements
• Specification or proposal URL:
  • Allow setting default accessibility semantics for custom elements whatwg/html#4658
  • https://github.com/alice/aom/blob/gh-pages/explainer.md#per-instance-dynamic-semantics-via-the-elementinternals-object
• Mozillians who can provide input (optional): Jamie Teh

Other information

This will allow Custom Elements to have "default" accessibility semantics, analogous to how built-in elements have "implicit" or "native" semantics.

e.g.

this._internals.role = "checkbox";
this._internals.ariaChecked = "false";

These can be overridden using regular ARIA attributes as normal.

This is currently being implemented in Blink, and we intend to ship this alongside Reflecting IDREF/IDREF list ARIA attributes to element references.

[dbaron]

cc @jcsteh

[annevk]

Improving the accessibility story of custom elements is important and this is something we'd like to see happen.

cc @hsinyi

[nschonni]

Just making the comment here instead of the PR, but I think this should be important given discussions like https://twitter.com/sarahmei/status/1198069119897047041 which have people avoiding aspects of web components given accessibility gotchas

[annevk]

To be clear, this is important, but in the end this is a small part of a much larger whole and we tend to use important for bigger things I think.

[nschonni]

OK, thanks for clarifying @annevk