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

> We already have one declarative way of achieving these accessibility characteristics and the related behaviors: the `is` attribute.

Agreed, it already covers everything mentioned in here, without the risk that some piece of accessibility is forgotten.

The reference link on how to create a custom button that actually **is** a button:
http://www.w3.org/TR/custom-elements/#custom-elements-customized-builtin-example

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