Earlier quoted context omitted.
The dismal accessibility adoption on the web is horrendous, but working for a company that has to deliver accessible web apps to comply with Federal law has really opened my eyes to how terrible to ecosystem of accessibility is. My team spends about a quarter of our time working strictly on accessibility, and we find ourselves straying from the beaten path often in order to accommodate a specific screenreader/OS comb…
Since website frameworks like Bootstrap are a thing, would it make sense to implement accessibility guidelines at that level, so that designers/people who don't know are encouraged to use sane defaults? Or is it too content/layout specific? Eg: I might like to roll my own static blog, but I don't know how to ensure that it is accessible.
One of the things we've learned is that much of the complex, dynamic UI things one can do with frameworks like React/Angular is really, really, really hard and frustrating to make fully accessible because people never design React components that are easy to use with a keyboard.
We live in this world where the capabilities of UIs for enabled people continue to grow at the cost of accessibility for the disabled. With the shift towards frontend frameworks, the problem needs to be addressed at the markup level IMO.