Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)

Adding the ability to specify the default role of a custom element seems like a sensible feature to have. Having to build your own accessibility tree just when simply setting the role would do the work is not a great developer ergonomics.

But we should probably start from the baby steps and just add `defaultRole` property to the list of options to `customElements.define`. That'll solve the majority of simple use cases.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/567#issuecomment-280886128