If you've taken calculus, you'll understand the idea of area under the curve- the number of people using your app will likely go up over time, and it takes time

If you've taken calculus, you'll understand the idea of area under the curve- the number of people using your app will likely go up over time, and it takes time to accrue customers (the area under the curve of the rate of customers). One thing that you should think about is that it takes time for products to gain momentum, and as a product gains momentum, it generates revenue. As such, it might make sense to ship your code without much accessibility support and add it in the ensuing months. If you can be available to even 50% of potential customers three months before the first scenario, by only releasing for people using the OS you develop on, and then you go cross-platform in three, (making your population ~90%) and then add accessibility in the sixth month, it would still make sense from a business point of view to do so. Keep in mind that things take time to develop a userbase, and that large companies really like things to have an established userbase and support before they get on board. For instance, one of the major reasons that the Raspberry Pi Foundation has seen so much success, even though they aren't the fastest or the cheapest, is because they have a large community support network and support their stuff well. As such, as long as I (and / or management) are committed to implementing solely-accessibility related features in the near future, I would take the first option, and release as soon as I could.