tactual-dev/tactual
by Various
Screen-reader navigation cost analyzer — models the real effort to discover, reach, and operate interactive web content
MCP
tactual-dev/tactual
Added 1 June 2026
Overview
Tactual is a TypeScript tool that models the effort required for screen-reader users to discover, reach, and operate interactive web content. It analyzes navigation costs based on accessibility tree structure and interaction sequences.
Best for
Best for
Frontend developers and accessibility engineers aiming to reduce navigation effort for screen-reader users
Use cases
- Audit web pages for screen-reader navigation bottlenecks
- Compare accessibility costs of different UI implementations
- Integrate into CI pipelines to prevent regressions in screen-reader user effort
Notes
Tactual is a TypeScript tool that models the effort required for screen-reader users to discover, reach, and operate interactive web content. It analyzes navigation costs based on accessibility tree structure and interaction sequences.
0 stars on GitHub. Last updated 2026-05-03. Licensed Apache-2.0.
Use cases
- Audit web pages for screen-reader navigation bottlenecks
- Compare accessibility costs of different UI implementations
- Integrate into CI pipelines to prevent regressions in screen-reader user effort
Pros
- Provides a quantitative metric for a traditionally qualitative accessibility concern
- Open source and integrates with standard web development tooling
- Models real user effort rather than just checking for static accessibility rules
Cons
- Still early-stage with no stars or community adoption on GitHub
- Requires understanding of screen-reader interaction patterns to interpret results
- May not cover all disabilities or assistive technologies beyond screen readers
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Provides a quantitative metric for a traditionally qualitative accessibility concern
- Open source and integrates with standard web development tooling
- Models real user effort rather than just checking for static accessibility rules
Cons
- Still early-stage with no stars or community adoption on GitHub
- Requires understanding of screen-reader interaction patterns to interpret results
- May not cover all disabilities or assistive technologies beyond screen readers
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.