Intent: research. For users who are blind or have low vision, touchscreens present a fundamental challenge: the interface provides no tactile landmarks.
Unlike physical keyboards with raised bumps on the F and J keys, or button panels with distinct shapes, a flat glass surface offers no inherent way to locate interface elements without sight.
Recent research on “TapNav”—an adaptive spatiotactile screen reader prototype—explores how tactile overlays combined with adaptive audio could address this gap. For anyone designing public touchscreen installations, the research offers both inspiration and practical considerations.
The Core Accessibility Challenge
Traditional screen readers work well for linear content—reading a webpage from top to bottom, navigating a document paragraph by paragraph. But touchscreen interfaces are inherently spatial:
- Grids of options that can be tapped in any order
- Maps that require spatial understanding of geography
- Interactive displays where the relationship between elements matters
Current accessibility solutions for touchscreens typically fall into two categories:
VoiceOver/TalkBack Approach
Mobile operating systems include gesture-based screen readers. Users explore by dragging a finger across the screen while audio announces elements under their touch. This works, but:
- Exploration is slow compared to visual scanning
- Spatial relationships aren’t conveyed (is this button above or below the last one?)
- Public kiosks may not support mobile accessibility gestures
Companion Device Approach
Some installations offer a separate accessible interface—a companion app, a tactile diagram, or a staff-assisted experience. This provides accessibility but not independence.
What TapNav Proposes
The TapNav research explores a middle path: adding tactile feedback directly to the touchscreen interface through physical overlays and adaptive audio.
Physical Tactile Overlays
Raised elements placed on the screen surface create tactile landmarks that users can feel. These might indicate:
- Button locations
- Navigation regions (top menu, main content, footer)
- Interactive versus static areas
The challenge: overlays must be designed for each interface layout. A single overlay works for a fixed-layout kiosk but not for dynamic content.
Adaptive Audio
Rather than simple text-to-speech, adaptive audio conveys spatial information:
- Stereo positioning indicates horizontal location
- Pitch variation indicates vertical position
- Audio “textures” differentiate content regions
Combined, these cues help users build a mental model of the interface layout—not just the content.
Implications for Public Installations
The TapNav research isn’t a product; it’s an exploration of possibilities. But the principles inform practical accessibility planning:
Design for Spatial Simplicity
Complex interfaces are harder to make accessible. Every additional element increases cognitive load for users navigating without sight.
Practical application: Limit touchscreen interfaces to essential functions. If the interface has 30 buttons, consider whether 10 would serve users better.
Provide Consistent Layouts
When interface layouts vary screen to screen, users must relearn navigation constantly. Consistent placement of back buttons, home links, and primary actions reduces friction.
Practical application: Create a layout template for your touchscreen software and stick to it across content types.
Consider Multi-Modal Alternatives
The best accessibility often isn’t making the touchscreen itself accessible—it’s providing alternative access paths:
- QR codes that link to web-accessible versions viewable on personal devices with preferred settings
- Audio descriptions triggered by touching screen regions
- Companion printed materials with tactile elements for critical wayfinding
Plan for ADA Compliance
Public installations in the United States must meet ADA requirements. Beyond touchscreen accessibility, this includes:
- Reach range: Controls between 15" and 48" from the floor
- Clear floor space: Wheelchair approach area
- Alternative access: For features that can’t be made fully accessible
WCAG 2.1 AA standards provide additional guidance for digital interfaces, including:
- Sufficient color contrast (4.5:1 for normal text)
- Text resizing support
- Keyboard navigability for web-based content
What Vendors Should Consider
If you’re evaluating touchscreen display software, ask vendors about accessibility:
- Does the software support screen reader compatibility? (For web-based interfaces)
- Can content be accessed via QR code on personal devices?
- What’s the minimum/maximum text size?
- Does the interface support high-contrast modes?
- How are videos and audio content captioned/described?
Vendors who haven’t considered accessibility may have difficulty answering these questions—which is itself useful information.
The Research Horizon
TapNav and similar projects point toward a future where touchscreen accessibility improves significantly. Emerging technologies include:
- Ultrasonic haptics: Creating tactile sensations in mid-air above the screen
- Refreshable tactile displays: Surfaces that physically change to create raised elements
- AI-powered scene description: Computer vision that describes visual content in real-time
These technologies remain largely in research phases, but exhibit designers should track developments. Today’s experimental prototypes often become tomorrow’s commercial products.
Conclusion
The gap between touchscreen potential and touchscreen accessibility remains significant. Research like TapNav offers paths forward, but practical accessibility today requires:
- Designing interfaces with simplicity and consistency
- Providing alternative access methods (QR codes, companion apps)
- Meeting baseline ADA/WCAG requirements
- Asking vendors specific accessibility questions
The best touchscreen installation is one that serves all users—not just those who can see the interface clearly.
For guidance on accessible touchscreen display implementations, see our comprehensive guide.
Best Touchscreen is an independent resource. We have no affiliation with the TapNav research team or any specific accessibility technology vendor.