Questions
So should I stop worrying about accessibility in my app?
No. Generated interfaces are built from what you ship today.
Our interviewees use today’s software today, and it has to work for them now. Standards and best practices are what made Myron’s setup possible at all.
And the shift we describe doesn’t replace that work, it builds on it. An AI that maps your app onto a fresh interface goes through what your app exposes: its APIs, its structure, its semantics. The better those are, the better what it can generate. Apps that are well built and well described are the ones a person’s own interface can use.
How would this be implemented, and does it work today?
Partly, and you can try it now by asking Claude. It’s the worst it will ever be.
This talk is about the people we interviewed and what they need, so we deliberately didn’t design an architecture for it. How it gets built matters less to us than who it gets built around.
And you don’t have to wait for one. Tell Claude what you’re trying to do and what it should know about you, and ask it to build you the interface: an artifact is a small app made on the spot for one task. Eight months after our first interview, Rose had built an app to organize her Steam library. It picks the game that fits her energy budget at that moment, and she keeps changing it as suits her. That’s the idea working, for one person, today.
It still took her a lot of time, and Rose is technical: she studies cyber security. Most people couldn’t do what she did yet. But the models are moving fast. Google Research found that generating a working interface is an emergent capability: their newest model produced valid interfaces for every prompt, while a model one generation older failed on 60% of them. It crossed a threshold rather than improving gradually.
So we don’t think the remaining effort is a property of the idea, just of today’s tools. We could be wrong, but we think it’s a matter of time.
Doesn’t a UI that keeps changing break screen readers?
Right: stability is basic to accessibility. An interface that understands you holds still.
The sharpest objection: if interfaces are generated, don’t you destroy what a screen reader user relies on, the button being where it was yesterday? Molly runs her screen reader fast because she knows her setup; Myron has memorised where things sit on his screen. A constantly re-rolling interface would be a disaster for both.
Our answer is memory. The interface is generated for you, then remembered and reused. And an empathetic interface applies least surprise: it knows you navigate by memory, so it holds still. Personalize the content, not the structure.
It’s today’s one-size-fits-all interface that changes under you, whenever its vendor redesigns it. That’s the Ravelry redesign that put Rose in bed for three days.