No worries. I was confrontational in my post. Let me clarify: I'm not saying MVP (or pre-profit product) developers should ignore accessibility. I'm saying the

No worries. I was confrontational in my post. Let me clarify: I'm not saying MVP (or pre-profit product) developers should ignore accessibility. I'm saying they shouldn't spend too high a portion of their time worrying about it. If a product fails some measure of accessibility it has a bug which will need to be fixed at some point. Just because it's a bug that you are aware of and it's easier to detect than other bugs doesn't mean that it should stop you from trying to sell the product. A buggy product with some income is more likely to succeed than an apparently bug-free product and no income. I've worked with blind coworkers in the past and have tried using screen readers myself so I have some appreciation of the challenges. Thank you for the link, it's always good to have a reminder. It sounds like the employer in question and Siebel should have had legal action taken against them. They're both clearly of a size where they can and should be doing better. This is another example of why we need brilliant web developers building businesses that can destroy backwards companies like those. How do you get on with Hacker News? I just put it through a checker and it appears to be pretty appalling. Would it be better if pg shut down Hacker News completely until the issues it found are resolved?