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

> Having accessibility implicitly inherited seems a better way to move the Web forward, and we should use `is` as much as we can for graceful enhancement and backward compatibility.

It’s important to note that not every browser agree with `is`. I personally think it feels quirky and is not the best solution we could have. I think these behaviors are a much more general solution. We could allow the `accessibilities` to be inherited from other elements, so that when you extend from `HTMLButtonElement`, even if you don’t get something that is *styled* like a button is, you do get something that behaves like a button. That is, you could very easily get a button‐like element by inheriting behavior from the actual button element:

```Javascript
customElements.define("my-button", class extends HTMLButtonElement {}); // inherits behaviors and default attribute values
```

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