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

@domenic would this cover all the behavior from a `button` element (i.e. focusability, disableability, the ability to be clicked with the space‐bar/enter), all without sprouting new attributes? What if someone wants to create their own behavior? Behaviors, besides accessibility, allow people to do things such as adding methods/properties to an element, adding event listeners and firing events, etc.

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