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

neither `tr`, the `script` itself ... you name it. I understand your idea but I don't think it'll help the Web to be more accessible in the long run.

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.

Adding yet another way to obtain a real button looks like something maybe considerable in a possible, future, V2, keeping `is` where it is now in specs.

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