Topic
Accessibility
Where a spoken interface is the accessible path rather than the convenient one.
5 posts
- An in-app agent is an accessibility feature, narrowlyAn agent that completes a task is an alternative input path, and one WCAG 2.2 criterion turns the biometric confirm into an accessibility win rather than a tax.Voice10 min
- Voice is an alternative input path, not a speed featureThe case for a spoken path into your app, argued from the curb-cut effect, WCAG 2.2 and what screen reader users actually report.Voice7 min
- Voice or chat: picking the mode for the taskSpeaking and typing are two inputs to the same agent. The situation the user is in decides which one wins, and four of those situations are predictable.Agent basics9 min
- Using an agent to get a user to first valueOnboarding leaks where people have to type. An agent can collapse setup into one request, and there are four kinds of friction it genuinely cannot touch.Business8 min
- Conversational interfaces and older users: the real tensionWhy asking for a task costs older users less than navigating to it, and why the same people are least likely to have tried an AI product.Voice8 min