aria-validate

ARIA Validate MCP Server is designed to verify ARIA attributes and roles using the aria-query library. It allows clients to pose questions about ARIA validity, such as whether aria-labelledby can be used with the navigation role, what values are valid for aria-hidden, or to obtain a list of all ARIA landmarks. The server processes these requests via the MCP protocol, enabling automated validation checks as part of your accessibility QA workflow. You can integrate it with an MCP client (for example Claude Desktop) and send queries to the aria-validate-mcp server to obtain precise, query-based responses about ARIA semantics and best practices.

Once configured in your MCP client, you can interact with the server to: (1) validate specific ARIA attributes in context, (2) query for valid value sets (e.g., allowed values for aria-hidden), and (3) enumerate ARIA landmarks and roles. The tool leverages aria-query under the hood to ensure the guidance reflects current ARIA specifications, helping you audit and reason about accessibility attributes in your UI code.

Prerequisites:

• Node.js 24.x or newer (for environments requiring Node-based tooling)
• Deno 2.x or newer (required by the aria-validate MCP server)

Installation steps:

1. Obtain the server source (clone the repository or download the package).

2. Ensure Deno is installed and available in your PATH. You can install Deno from https://deno.land/#installation.

3. Prepare the server entry point. The MCP server expects an index.ts at the specified path. For example, place your server entry at /path/to/aria-validate-mcp-server/index.ts.

4. Run the MCP server using Deno. A typical command looks like: deno run --allow-read /path/to/aria-validate-mcp-server/index.ts

5. Configure your MCP client to connect to the server. In the client configuration, specify: { "mcpServers": { "aria-validate-mcp": { "command": "deno", "args": [ "run", "--allow-read", "/path/to/aria-validate-mcp-server/index.ts" ] } } }

6. Start using the MCP client to send queries to aria-validate-mcp and receive validation responses.

Note: Adjust paths and environment permissions as needed for your deployment environment.

Tips and considerations:

• Ensure Deno permissions (--allow-read) are correctly set for the server to access necessary resources.
• Keep aria-query up-to-date in your environment to reflect the latest ARIA specification changes.
• If you encounter permission or path issues, verify that the path to index.ts is correct and that the MCP client is configured to point to the running server.
• This MCP server focuses on ARIA attribute and role validation; for broader accessibility checks, consider combining it with other MCP servers in your workflow.
• Environment variables are not strictly required by default, but you can add placeholders or real values for logging, debugging, or feature toggles as needed in a production setup.