|
|
|
|
|
by ctoth
4915 days ago
|
|
This is an absolutely terrible idea that seems to refuse to die.
No, it is not reasonable to put the accessible content in some sort of blind-only ghetto. Amazon do this, for instance, with a text-based version of their website. It makes it more difficult to maintain unless you've architected from the absolute beginning for it, and over time the text-based version becomes useless.
Think of it from the perspective of someone adding new features to your webapp. Let's put it in HN terms -- you're building your MVP, launching in three days or something absurd... Are you really going to go build a text-based version of your website? Are you going to keep that updated?
No. The only solution is to make the actual web, the one we all use, accessible. This doesn't mean changing what individual developers do so much as making sure that it's harder to be inaccessible than to be accessible with technical fixes, I.E. fixing Bootstrap so all Bootstrap sites are more accessible. |
|
Startups have a good chance to start their framework with accessibility in mind.
An MVP could ignore this aspect, because it is not the final product yet.