with the latest webdev trends it is extremely unlikely this will improve any time soon. There was a time (~10-15) years ago when separation of concenrs and accessibility did matter, now it is just a js frameworks bloodbath.
Some "frameworks" put a ton of work into accessibility.
The Polymer team's entire element catalog is accessible with ARIA integration done with assistance from Chrome's dedicated accessibility engineers. We even provide reusable abstractions that make writing your own accessible elements easier, like iron-a11y-announcer and iron-a11y-keys.
Thanks for the link - was really interesting, particularly the introduction which explains why accessibility is so important and the number of people that it touches.
The Polymer team's entire element catalog is accessible with ARIA integration done with assistance from Chrome's dedicated accessibility engineers. We even provide reusable abstractions that make writing your own accessible elements easier, like iron-a11y-announcer and iron-a11y-keys.
Accessibility was a big topic at our last Polymer Summit: https://www.youtube.com/watch?v=o6yLWihykVA