[ijwann]

Good luck getting your organization to support building two apps. And even if you succeed once, good luck getting your organization to ship features twice every single time they want to build something.

What will end up happening is you have your normal app which isn't accessible, and a second app with a fraction of your features that is likely often broken because it's hard to prioritize.

[threatofrain]

You have one backend and two frontends, one of which is simplified and all-about-the-data. I daresay there's the possibility that it's easier to create two websites than it is to make one website do two things.

[extra88]

You might have heard of this thing called "responsive web design," (RWD) it's pretty popular. RWD is all about it not being better to make two websites (in that case, "mobile" vs. "desktop") instead of one.

[threatofrain]

In some ways this is similar. With responsive design we're talking about orthogonal views in the sense that given enough effort, the mobile and desktop experiences can be completely different, but of course in practice we're going to reuse components to save time.

So just like we have desktop and mobile views, I'm just proposing one more view where you also get to reuse some of your components, and where you get to pushback on stuff like animations, rich interactions, or novelties.

[extra88]

There are already ways to make all those things conditional without creating an entirely new view.

Only occasionally does the "accessible way" need to be in addition to what was planned all along, such as up, down, left, right arrow buttons beside a draggable map, you don't need a whole separate map for that.