[septerr]

Why shouldn't companies (their developers) put in the extra effort needed to keep both versions up to date? They can come up with a framework for it. It may not necessarily mean two totally separate code base. You could design your framework so that both versions feed off the same backend. And don't they have to put in that extra effort to make sure their mobile versions are up to date?

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.

[ctoth]

Because they won't. I'm commenting from the perspective of a blind user--I know of what I speak. Note that I explicitly said you would have to architect for it, which you reiterated in your point. Doesn't it make far more sense to make the underlying tooling accessible rather than ghettoizing the content? My main point here is, if there's extra work to be done to make content accessible, that work simply won't be done. Hell, I wouldn't do it either -- a whole extra site template's worth for what? 1% of users? and I am totally blind.