Screen readers navigate by landmarks, headings, and Tab order, but most accessibility tooling stops at markup validation. This server surfaces the actual keystroke cost to discover and reach interactive targets under NVDA, JAWS, or VoiceOver profiles. It exposes analyze_url and analyze_pages tools that return findings with selectors, navigation paths, scoring breakdowns, and suggested fixes. Use it when you need to measure navigation effort in staging environments, diff before and after scores in CI, or trace why a checkout button takes forty Tab stops to reach. It complements axe and Lighthouse by answering the next question: given valid ARIA, how expensive is this interface for AT users?
claude mcp add --transport stdio tactual-dev-tactual -- npx -y tactual