Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

I don't get why people keep making claims that `is=` improves accessibility.  It simply doesn't except the very simple scenario in which the entire UI of the builtin form control is preserved (e.g. just adding JS methods).

In reality, a lot of custom form controls exist on the web for the sole purpose of customizing appearances against their builtin counterparts.  Unfortunately, as soon as you've attached shadow root on a builtin element [which is not even supported in shadow DOM v1](http://w3c.github.io/webcomponents/spec/shadow/#widl-Element-attachShadow-ShadowRoot-ShadowRootInit-shadowRootInitDict), there is no accessibility benefit from using `is=` because UA can't determine how elements in a shadow tree corresponds to what UI actions without explicit annotations by the author.

---
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/509#issuecomment-230884238