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

@domenic sorry, but I can’t seem to understand this “a11y-api” you linked. How would you, say, create an element that acts like a button? With my suggestion, that would be trivial. You’d just have to write `customElements.define("my-button", {behaviors:{"button-like":{}}})` with the very short “`button-like`” behavior defined in the OP.

-- 
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-247047904