I don't think that's a reasonable comment. Any business first needs to address a marketplace that's enough to sustain itself and assure it's future existence. B

I don't think that's a reasonable comment. Any business first needs to address a marketplace that's enough to sustain itself and assure it's future existence. Beer chased men because more men drank, then when more woman started to drink it they started advertising to it. While that's perhaps a different example due to one group not being actually excluded from something it shows how business behaves. Then you consider the risk of staying a startup to your future, your retirement, the funders cash/investment and honestly I'd you spent a dime on accessibility at this stage it would be reckless behavior. Now having said that, once a product mix and the positive trajectory path has been established, then I don't think it's reasonable to delay, not even to say 'wait until we are profitable', because at that point you need to start addressing access to everyone equally as part of your business and if your business cannot sustain itself being inclusive then it's best to establish that earlier than later IMO. Ps. I'm in no way poo pooing your point about the needing to be more training around accessibility, because ultimately that's part of the meat and potatoes of bring a dev. Like knowing SQL, JS, etc. All part of the basic skills we all need to survive most days at work. And accessibility is in the group. I'm only saying that a startup needs to first determine demand for it's product with the largest addressable group in it's core target audience, then branching out should immediately include accessibility IMO.