a11y

Provides accessibility auditing and WCAG lookup, with remediation guidance and component documentation via an MCP endpoint.
  • javascript

0

GitHub Stars

javascript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You can run an MCP server that provides accessibility auditing, WCAG lookup, remediation guidance, and component documentation. This server exposes practical tools you can use to look up WCAG criteria, analyze HTML snippets for accessibility issues, generate remediation patterns, and produce formal accessibility documentation for UI components. It also supports deploying to hosting providers and testing locally before going live.

How to use

You interact with the server through a client that speaks the MCP protocol. Use the server to look up WCAG criteria by number, keyword, or level; analyze HTML snippets for common accessibility issues; request remediation patterns with before/after examples; generate accessibility documentation for UI components; and compile professional audit summaries from a list of issues.

How to install

Prerequisites you need before getting started are Node.js version 18 or newer and npm. You will install dependencies, build the project, and run the server locally to verify it works before deploying.

# Install dependencies
npm install

# Build the project
npm run build

# Run locally
npm start

Deployment and configuration

You can deploy the server to a hosting environment and expose the MCP endpoint under /mcp. A health check and the MCP endpoint are available once the server is deployed.

Local development and testing with a hosting setup are described in the following steps.

NFSN deployment involves creating a site, uploading code, configuring a daemon to run the server, and configuring a proxy so that requests to /mcp reach the server port. You can verify deployment with a health check and a POST request to the MCP endpoint.

Deployment steps overview

  1. Prepare a site on your hosting provider and note the site hostname.

  2. Upload code to the server using a file transfer method appropriate for your hosting provider.

  3. Install dependencies on the host, then build the project, and ensure the runtime script is executable.

  4. Create a daemon that runs the server using the appropriate startup command and working directory.

  5. Configure a proxy so that requests to /mcp are forwarded to the server’s port (commonly 8080). Verify the health and MCP endpoints after deployment.

Troubleshooting

If the server does not respond as expected, check the daemon logs to identify startup errors, verify the process is running, and ensure the proxy is correctly forwarding requests to the server port.

Notes on testing with Claude Code and local testing

For local testing with Claude Code, start the server locally and configure Claude Code to connect to the local MCP endpoint. Add the local MCP URL to Claude Code configuration so you can validate WCAG lookups, patterns, and documentation generation in a local environment.

Usage examples

Look up a WCAG criterion, analyze HTML for accessibility issues, request a remediation pattern, or generate component documentation through your MCP client by calling the corresponding endpoints exposed at the /mcp path.

Security and maintenance notes

Keep Node.js and dependencies up to date by applying regular npm install and builds. Monitor health and error logs to detect issues early. When deploying to production, ensure TLS termination at the proxy and restrict access to the MCP endpoint as needed.

FAQ and tips

If you need to test features locally, run the server with npm start and point your MCP client to http://localhost:8080/mcp. For remote deployment, ensure the proxy base path is /mcp and the target port matches the server’s listening port.

Available tools

a11y_lookup_wcag

Look up WCAG 2.2 criteria by number, keyword, or level to retrieve details including guidance and applicability.

a11y_check_pattern

Analyze HTML snippets to identify common accessibility issues and surface actionable fixes.

a11y_suggest_fix

Provide remediation patterns with before/after code examples to address identified issues.

a11y_document_component

Generate accessibility documentation for UI components, including interactions, ARIA attributes, and screen reader expectations.

a11y_audit_summary

Create professional audit summaries from an issues list for formal reporting.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational