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

I prefer the solution given by https://github.com/a11y-api/a11y-api/, which allows manipulation of the actual primitive involved (the accessibility tree) without tying the solution to custom elements or creating a bunch of new concepts like behaviors with declarative matches and defaults.

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