I doubt it. There is nothing that states API is required for accessibility. There are common, easy to implement design tools to improve accessibility.
Look at the WCAG guidelines (https://www.w3.org/TR/WCAG21/) for exactly what you should be doing (also for a look at what a truly accessible site looks like).
These are not difficult things to implement and do not require third party, or even first party apps to do. They can easily be integrated into any website.
It’s not a requirement now. I meant that there would be new legislation to expand ADA to cover API requirements.
APIs aren’t expensive to implement, but they reduce revenue since people bypass ads and weaken moats as data is more portable. Companies are choosing to drop and not build because of revenue, not cost.
So the problem with that is that (a) it requires a full update or amendments to the ADA, and (b) it requires legislators to understand what an API i and what it does.
For point (a): We went from 1990 to 2008 before the ADA was last amended. So, according to that precedent, we will be waiting until 2026 or so. I guess that's not too bad. But my money says it's 2040+ before we see that amended again.
For point (b): It feels like this one may be like asking if you can lick a rainbow.
There’s already a portion called “section 508” [0] that requires software and web sites to be accessible, but it only applies to federal procurement.
An extension could be that apis are required for accessibility and that they apply to all businesses over a certain size.
While Section508 is designed for people with disabilities they affect all users since what helps screen readers also helps screen scrapers, etc. etc
[0] https://www.section508.gov/manage/laws-and-policies/