But I'd much rather work at a company that was 1% less profitable or live in a society that was 1% less wealthy and accommodated people with disabilities than one that left them in the gutter.
At least with webdev the problem is most people stumble into it and are not formally taught much about webdev specifically if at all. My undergrad never taught me a single thing about webdev practice. It’s not like, say, architecture, where you not complying with accessibility regulations will be taught formally, or later when you actually implement it some code compliance inspector is going to deny you a permit to build. It really is the wild west in webdev still.
In my view, it's about trying to provide more 'equal opportunity' in this world where it's financially feasible. This seems like a case where it is more often that not. Again, for medium+ businesses.
EDIT: By analogy, it's very like software portability. If you make your software support Windows and MacOS and assorted Linux distros and the major BSDs and Haiku, you'll get more users. But if you only target Windows you'll get 80% of the market, and Windows+MacOS will get you 90%, and after that you really need to think about whether it's a good investment to target more platforms. By all means, be accessible because it's the right thing to do or legally required, but it's not obvious that it's a sound business move.