> There's no incentive to do so Well, the incentives to do so aren't obvious. Having worked on a bunch of (a) web applications with no dynamic client behavior

> There's no incentive to do so Well, the incentives to do so aren't obvious. Having worked on a bunch of (a) web applications with no dynamic client behavior to speak of (b) SPAs that are essentially a dynamic client talking to a service layer speaking JSON and/or XML (c) things in between... I think I've noticed a pattern, and it's that web applications where people take the time to think about how things would work with no dynamic client behavior, going through a process that more or less represents domain logic as HTTP operations on resources that can be represented as HTML (among other representations), these applications end up being more legible over time than projects with client engineering/experience as most of the focus. Not all applications fit this model, so there are limits to the approach. And accessibility is a somewhat different domain. But the concerns overlap, so one tl;dr might be this: Site accessibility is one canary in the web application mines. If it's dead, you might be accumulating technical debt.