Skip to main content
Maximum automation.

The platform for digital accessibility

navable combines WCAG audits, audit history, statement drafts and developer tools. Review findings, plan fixes and document your team’s progress.

Start with a 7-day free trial
Automated WCAG audits
Developer & AI tools
Statement drafts from audit data
Microsoft for Startups Partner Badge

navable is developed as part of the Microsoft for Startups program.

🇩🇪 Made in Germany, with focus on high-quality accessibility solutions.

Aligned with the standards that matter:

  • WCAG 2.1 & 2.2
  • EN 301 549
  • BFSG
  • EAA
  • BITV 2.0
  • Section 508
All-in-one platform

One platform instead of scanners, spreadsheets, and PDFs

Accessibility rarely fails because of a missing scan. It fails because the workflow is fragmented. navable connects audit, remediation, monitoring, and documentation in one source of truth.

One dashboard, every workflow

Scan, prioritize, fix, monitor and declare — track your accessibility score over time and show stakeholders real progress.

Explore the platform

Deeper audits

Test websites and web apps across devices, flows, and page states — including areas simple scanners cannot reach.

Developer & AI tools

Bring findings, fix prompts, and audit data directly into IDEs, AI agents, and CI/CD workflows.

Documentation without rework

Generate accessibility statements and VPAT/ACR documents from real audit data instead of static templates.

Monitoring over time

History and alerts available in Audit

Compare earlier and current findings in Audit. Use score history and alerts to investigate regressions after releases.

To Audit · Alerts & score history

Beyond text: seeing controls and focus

Borders, icons and focus indicators need at least 3:1 contrast against the adjacent colour when they identify a control or its state. Decorative borders and disabled controls are exempt. Check focus and selected states manually too.

See examples of borders, focus and selected statesWCAG 1.4.11: requirements and exceptions
Beyond a standard scan

Test modals, cookie banners and login flows

navable tests websites after user actions, such as opening a dialog, choosing cookie settings or logging in. Plan these states in your website test and use Audit for automated checks. Add manual keyboard and screen reader tests.

AI semantic analysis

Evaluates what static rules cannot: for example, whether alt text truly describes the image, whether a link's purpose is clear, or whether headings match the real structure.

AI Path-Finder & User Flows

Describe a goal in plain language. navable discovers and tests the required steps automatically.

Multi-device audits

Audit desktop and mobile in one run to catch responsive barriers earlier.

Multi-state audits

Test modals, error states, banners, and other states users actually experience.

Plan test scope with the website testing checklist
Developer & AI experience

Check localhost for WCAG errors without an account

Use the free open-source local MCP in your IDE: scan a page, address findings in code and re-scan. The local MCP needs no navable account; the hosted MCP accesses audit data in your account.

Hosted MCP server

Query live audit data directly from VS Code, Cursor, or Windsurf.

Open-source local MCP

Scan localhost locally with Playwright and axe-core, without a navable account or API key.

Agent skills

Use repeatable scan → fix → verify workflows for accessibility work.

REST API and CI/CD

Trigger audits automatically after deploys or integrate accessibility into existing pipelines.

Set up the local MCP in VS Code

Create .vscode/mcp.json in your project. After starting the MCP server, give your agent the local URL to test.

{
  "servers": {
    "navable": {
      "command": "npx",
      "args": ["-y", "@navable/mcp"]
    }
  }
}

Then ask your agent:

Scan http://localhost:3000 for accessibility issues

Setup for Cursor and Claude CodeExplore developer workflows

Every finding ships with a copy-paste fix prompt for AI code editors.

Explore developer tools
Document & stay on top of it

From audit findings to a published accessibility statement

The biggest manual effort often starts after the audit. navable connects findings, evidence, and statement generation in one workflow.

Accessibility statements

Create an editable accessibility statement draft from your audit data. Review its content and testing scope before publication.

VPAT/ACR documentation

Use the same source data for procurement-facing documentation and partner requirements.

Alerts and reports

Keep teams informed automatically with email and Slack notifications.

Jira, Notion & GitHub

Push issues into the tools your team already works in.

Why teams move from point tools to navable

The question is rarely whether a scanner is needed. The real question is whether accessibility remains a one-off project or becomes a repeatable workflow.

One platform instead of a tool stack
Fewer handoffs, less duplicate work, less documentation chaos.
Honest automation
navable automates as much as possible and stays transparent about where human review still matters.
Depth beyond surface scans
Audit behind logins, across devices, and through dynamic states.
Useful for technical and non-technical teams
Developers get fix prompts, MCPs, APIs, and more, stakeholders get reports and documentation.
Documented & verifiable
From audit reports to accessibility statements and VPATs, navable produces the evidence you need.
Made in Germany
Built in Germany. The privacy policy describes hosting, data processing and the services we use.

View privacy details and services

Platform vs. point tools

Criterianavable platformBasic scannersOne-off agency / audit processes
Automated WCAG testingYesPartialRarely continuous
Login and flow auditsYesUsually noPartly manual
Multi-device / multi-stateYesLimitedPartial
Monitoring over timeIn Audit (score history & alerts)LimitedUsually external
Developer workflowsYesRareNo
Accessibility statementsIntegratedExternal / manualManual
One source of truthYesNoNo

Start lean. Expand when needed.

Start with a self-serve plan and expand your accessibility workflow over time. Pro and Business plans support deeper audit, monitoring, and documentation needs.

Basic

For Single SMBs (7-day free trial)

35€/Monthly

Prices shown per month when subscribing for 1 year

  • navable Widget
  • Page visits: 100,000
  • Number of supported pages: unlimited
  • Automatic Progressive Accessibility Enhancements
  • navable Audit
  • Number of Audits per Month: 50
  • On-Demand Scans
  • AI Fix Prompts for IDEs
  • navable Accessibility Statement AI Generator
  • LLM (AI Model): Standard
  • General
  • Support: Email support
Get started
Most popular

Pro

For Growing SMBs (7-day free trial)

85€/Monthly

Prices shown per month when subscribing for 1 year

  • Everything in Basic
  • navable Widget
  • Page visits: 1,000,000
  • Customizable
  • No Branding
  • navable Audit
  • Number of Audits per Month: 100
  • Scheduled Audit Runs
  • Reporting (Download + Mail)
  • Analytics / History
  • AI Semantic Web Accessibility Analysis
  • AI Path Finder (Flow Audits)
  • Multi-Stage State Audits (Single URL)
  • navable Accessibility Statement AI Generator
  • LLM (AI Model): Premium
  • General
  • Support: Priority email support
Get started

Business

For bigger SMBs and Enterprises

Contact Us

Custom extensions and pricing available

  • Everything in Pro
  • navable Widget
  • Page visits: unlimited
  • navable Audit
  • Number of Audits per Month: Custom
  • Webhook Integration for Audit Runs
  • VPAT AI Generator
  • General
  • Support: Priority support
Contact Us

Frequently asked questions

Under the BFSG, many digital services for consumers (B2C) must be accessible, including online shops, booking portals, customer areas, and banking applications. Whether a website is affected depends on the service, target audience, and business model. navable helps teams test digital accessibility in a structured way and determine the next steps for BFSG readiness.

A website can be tested for accessibility using automated WCAG scans, deeper real-browser audits, and complementary manual checks. navable combines these steps into one platform, showing not only violations on static pages, but also issues in interactive areas, responsive views, and complex user flows.

Traditional scanners typically only check static, publicly accessible page loads. navable uses real-browser testing to audit login areas, cookie banners, search forms, modals, dropdowns, responsive mobile views, and multi-step user paths that standard tools often miss.

Yes. With the AI PathFinder and configurable interaction steps, navable can close cookie banners, log into protected areas, and test multi-step user flows. This ensures accessibility is audited where real user interaction happens and simple website checks reach their limits.

navable connects audit data, monitoring, and documentation in one workflow. On this basis, teams can generate a structured accessibility statement according to BFSG/EAA and – depending on their needs – VPAT/ACR documentation from real audit data, instead of working with static templates.

No, automated checks alone are not enough for complete WCAG compliance. However, navable automates a large part of the audit and documentation process, supports deeper technical testing, and allows teams or external auditors to add manual findings to a shared data repository.

Every finding in navable can be processed with AI fix prompts, detailed WCAG guides, and developer workflows. Additionally, teams can access audit data directly from tools like VS Code or Cursor via MCP servers, the REST API, and IDE integrations, rather than working in a separate dashboard.

An audit checks selected pages and states at a particular point in time. Repeated audits with score history and alerts help you compare changes after releases. Start on the Audit product page. A dedicated monitoring product page is not available yet; the interim path leads to Audit.