@mcptoolshop/a11y-mcp-tools 0.3.0

package/.github/workflows/ci.yml

@@ -0,0 +1,53 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x, 22.x]
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Run tests
+      run: npm test
+
+    - name: Verify CLI works
+      run: |
+        node bin/cli.js evidence --target fixtures/html/index.html --dom-snapshot --out test-output.json
+        test -f test-output.json
+
+  lint:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20.x'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Check for syntax errors
+      run: node --check bin/cli.js bin/server.js src/index.js

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -0,0 +1,136 @@
+# Contributing to a11y-mcp-tools
+
+Thank you for your interest in contributing to a11y-mcp-tools! We appreciate your help in making web accessibility testing more robust and evidence-based.
+
+## How to Contribute
+
+### Reporting Issues
+
+If you find a bug or have a suggestion:
+
+1. Check if the issue already exists in [GitHub Issues](https://github.com/mcp-tool-shop/a11y-mcp-tools/issues)
+2. If not, create a new issue with:
+   - A clear, descriptive title
+   - Steps to reproduce (for bugs)
+   - Expected vs. actual behavior
+   - Your environment (Node version, OS)
+   - Sample HTML if relevant
+
+### Contributing Code
+
+1. **Fork the repository** and create a branch from `main`
+2. **Set up your development environment**
+   ```bash
+   npm install
+   ```
+3. **Make your changes**
+   - Follow the existing code style
+   - Add tests for new functionality
+   - Ensure all tests pass: `npm test`
+   - Update documentation as needed
+4. **Commit your changes**
+   - Use clear, descriptive commit messages
+   - Reference issue numbers when applicable
+5. **Submit a pull request**
+   - Describe what your PR does and why
+   - Link to related issues
+
+### Development Workflow
+
+```bash
+# Install dependencies
+npm install
+
+# Run tests
+npm test
+
+# Test CLI locally
+node bin/cli.js evidence --target fixtures/html/example.html --dom-snapshot
+
+# Test MCP server locally
+node bin/server.js
+```
+
+### Testing
+
+All new features should include tests. Tests are located in the `test/` directory and use Node's built-in test runner.
+
+```javascript
+// Example test structure
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+
+test('should detect accessibility issue', () => {
+  // Arrange
+  const html = '<img src="test.jpg">';
+  
+  // Act
+  const result = diagnose({ html });
+  
+  // Assert
+  assert.equal(result.findings.length, 1);
+  assert.equal(result.findings[0].rule, 'alt');
+});
+```
+
+### Adding New WCAG Rules
+
+1. Add rule implementation in `src/rules/`
+2. Add test cases in `test/*.test.js`
+3. Update README.md with rule documentation
+4. Add method ID to PROV_METHODS_CATALOG.md
+5. Update schemas if needed
+
+### Code Style
+
+- Use ES modules (`import`/`export`)
+- Prefer `const` over `let`
+- Use descriptive variable names
+- Add JSDoc comments for public APIs
+- Follow existing patterns for consistency
+
+### MCP Envelope Design Principles
+
+- **Tamper-evident** - All evidence includes integrity digests
+- **Traceable** - Provenance records for all operations
+- **Deterministic** - Same input produces same output
+- **Evidence-anchored** - Findings reference specific artifact locations
+- **SAFE guidance** - Fix suggestions describe intent, not direct code writes
+
+## Project Structure
+
+```
+a11y-mcp-tools/
+├── bin/               # CLI and server entry points
+├── src/               # Source code
+│   ├── tools/         # MCP tool implementations
+│   ├── rules/         # WCAG rule checkers
+│   ├── schemas/       # JSON schemas
+│   └── index.js       # Main exports
+├── test/              # Test suite
+├── fixtures/          # Test fixtures
+└── package.json       # Project configuration
+```
+
+## Schema Validation
+
+All requests and responses must validate against JSON schemas in `src/schemas/`:
+- `envelope.schema.v0.1.json` - MCP envelope format
+- `evidence.bundle.schema.v0.1.json` - Evidence bundle
+- `diagnosis.schema.v0.1.json` - Diagnosis output
+
+## Exit Codes
+
+Maintain CI-native exit codes:
+- `0` - Success (no findings at/above severity threshold)
+- `2` - Findings exist (operation succeeded, but issues found)
+- `3` - Capture/validation failure
+- `4` - Provenance verification failed
+
+## Code of Conduct
+
+Please note that this project is released with a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you agree to abide by its terms.
+
+## Questions?
+
+Open an issue or start a discussion. We're here to help!

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 mcp-tool-shop
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/PROV_METHODS_CATALOG.md

@@ -0,0 +1,104 @@
+# Provenance Method ID Catalog (v0.1)
+
+Stable method IDs for provenance tracking in a11y-mcp-tools.
+
+These IDs are **locked** and MUST NOT change within a major version.
+See [prov-spec](https://github.com/mcp-tool-shop/prov-spec) for the full specification.
+
+## Envelope Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `adapter.wrap.envelope_v0_1` | Wrap request/response in MCP envelope |
+
+## Provenance Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `adapter.provenance.record_v0_1` | Create provenance record with inputs/outputs |
+
+## Integrity Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `adapter.integrity.sha256_v0_1` | SHA-256 digest for artifact integrity |
+
+## Evidence Capture Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `engine.capture.html_canonicalize_v0_1` | Capture HTML with canonicalization (sorted attrs, normalized whitespace) |
+| `engine.capture.dom_snapshot_v0_1` | Extract DOM snapshot as flat node array |
+| `engine.capture.file_v0_1` | Generic file capture (CLI logs, etc.) |
+
+## Diagnosis Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `engine.diagnose.wcag_rules_v0_1` | Evaluate WCAG accessibility rules |
+
+## Evidence Extraction Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `engine.extract.evidence.json_pointer_v0_1` | Extract evidence anchor via JSON Pointer (RFC 6901) |
+| `engine.extract.evidence.selector_v0_1` | Extract evidence anchor via CSS selector |
+
+## Fix Guidance Methods
+
+| Method ID | Description |
+|-----------|-------------|
+| `engine.generate.fix_guidance_v0_1` | Generate SAFE-only fix guidance (intent patches) |
+
+---
+
+## Method ID Naming Convention
+
+```
+<namespace>.<action>.<target>_v<major>_<minor>
+```
+
+**Namespaces:**
+- `adapter.*` - Data transformation, wrapping, integrity
+- `engine.*` - Core processing (capture, diagnose, extract)
+
+**Versioning:**
+- Method IDs include version suffix (e.g., `_v0_1`)
+- Breaking changes require new method ID
+- Minor changes (backwards-compatible) use same ID
+
+## Usage in Provenance Records
+
+```json
+{
+  "provenance": {
+    "record_id": "prov:record:abc123",
+    "methods": [
+      "adapter.wrap.envelope_v0_1",
+      "adapter.provenance.record_v0_1",
+      "adapter.integrity.sha256_v0_1",
+      "engine.capture.html_canonicalize_v0_1",
+      "engine.capture.dom_snapshot_v0_1"
+    ],
+    "inputs": ["html/index.html"],
+    "outputs": ["artifact:html:index", "artifact:dom:index"],
+    "verified": false,
+    "created_at": "2026-01-27T04:12:00Z"
+  }
+}
+```
+
+## Adding New Methods
+
+1. Choose appropriate namespace (`adapter.*` or `engine.*`)
+2. Use descriptive action + target naming
+3. Include version suffix
+4. Add to this catalog with description
+5. Update `src/schemas/provenance.js`
+
+## Related
+
+- [prov-spec](https://github.com/mcp-tool-shop/prov-spec) - Full provenance specification
+- [envelope.schema.v0.1.json](src/schemas/envelope.schema.v0.1.json) - MCP envelope schema
+- [evidence.bundle.schema.v0.1.json](src/schemas/evidence.bundle.schema.v0.1.json) - Bundle schema
+- [diagnosis.schema.v0.1.json](src/schemas/diagnosis.schema.v0.1.json) - Diagnosis schema

package/README.md

@@ -0,0 +1,168 @@
+# a11y-mcp-tools
+
+MCP (Model Context Protocol) tools for accessibility evidence capture and diagnosis.
+
+## Tools
+
+### `a11y.evidence`
+
+Capture tamper-evident evidence bundles from HTML files, CLI logs, or other inputs.
+
+**Capabilities:**
+- Canonical HTML normalization
+- DOM snapshot extraction
+- SHA-256 integrity digests
+- prov-spec provenance records
+
+### `a11y.diagnose`
+
+Run deterministic accessibility checks over evidence bundles.
+
+**Capabilities:**
+- WCAG 2.2 AA rule checking
+- Evidence-anchored findings (JSON Pointer, CSS selector, line spans)
+- SAFE-only fix guidance (intent patches, not direct writes)
+- Provenance verification
+
+## Installation
+
+```bash
+npm install -g a11y-mcp-tools
+```
+
+## Usage
+
+### CLI (Recommended)
+
+```bash
+# Capture evidence from HTML file
+a11y evidence --target index.html --dom-snapshot --out evidence.json
+
+# Diagnose captured evidence
+a11y diagnose --bundle evidence.json --fix
+
+# With provenance verification
+a11y diagnose --bundle evidence.json --verify-provenance --fix
+
+# Output with MCP envelope
+a11y evidence --target page.html --dom-snapshot --envelope
+
+# One-liner capture and diagnose
+a11y evidence --target page.html --dom-snapshot | a11y diagnose --fix
+```
+
+**Exit Codes (CI-native):**
+- `0` - Success (no findings at/above `--fail-on`)
+- `2` - Findings exist (tool succeeded, but issues found)
+- `3` - Capture/validation failure (bad input, schema error)
+- `4` - Provenance verification failed (digest mismatch)
+
+### As MCP Server
+
+```bash
+a11y-mcp
+```
+
+### MCP Envelope Format (v0.1)
+
+Requests and responses use a standard envelope:
+
+**Request:**
+```json
+{
+  "mcp": {
+    "envelope": "mcp.envelope_v0_1",
+    "request_id": "req_01HR9Y6GQ7V8WQ0K8N9K",
+    "tool": "a11y.evidence",
+    "client": { "name": "a11y-cli", "version": "0.2.0" }
+  },
+  "input": {
+    "targets": [{ "kind": "file", "path": "html/index.html" }],
+    "capture": { "html": { "canonicalize": true }, "dom": { "snapshot": true } }
+  }
+}
+```
+
+**Response:**
+```json
+{
+  "mcp": {
+    "envelope": "mcp.envelope_v0_1",
+    "request_id": "req_01HR9Y6GQ7V8WQ0K8N9K",
+    "tool": "a11y.evidence",
+    "ok": true
+  },
+  "result": {
+    "bundle": { ... }
+  }
+}
+```
+
+**Error:**
+```json
+{
+  "mcp": {
+    "envelope": "mcp.envelope_v0_1",
+    "request_id": "req_01HR9Y6GQ7V8WQ0K8N9K",
+    "tool": "a11y.diagnose",
+    "ok": false
+  },
+  "error": {
+    "code": "PROVENANCE_VERIFICATION_FAILED",
+    "message": "Evidence digest mismatch for artifact:dom:index.",
+    "fix": "Re-run a11y.evidence to recapture evidence."
+  }
+}
+```
+
+## Schemas
+
+JSON Schemas are provided for validation:
+
+- [`envelope.schema.v0.1.json`](src/schemas/envelope.schema.v0.1.json) - MCP envelope format
+- [`evidence.bundle.schema.v0.1.json`](src/schemas/evidence.bundle.schema.v0.1.json) - Evidence bundle format
+- [`diagnosis.schema.v0.1.json`](src/schemas/diagnosis.schema.v0.1.json) - Diagnosis output format
+
+## Method ID Catalog (v0.1)
+
+Stable method IDs for provenance tracking. See [PROV_METHODS_CATALOG.md](PROV_METHODS_CATALOG.md) for full documentation.
+
+| Method ID | Description |
+|-----------|-------------|
+| `adapter.wrap.envelope_v0_1` | Wrap in MCP envelope |
+| `adapter.provenance.record_v0_1` | Provenance record creation |
+| `adapter.integrity.sha256_v0_1` | SHA-256 integrity verification |
+| `engine.capture.html_canonicalize_v0_1` | HTML capture with canonicalization |
+| `engine.capture.dom_snapshot_v0_1` | DOM snapshot extraction |
+| `engine.diagnose.wcag_rules_v0_1` | WCAG rule evaluation |
+| `engine.extract.evidence.json_pointer_v0_1` | JSON Pointer evidence extraction |
+| `engine.extract.evidence.selector_v0_1` | CSS selector evidence extraction |
+
+## Shared Artifact Model
+
+Both tools work with a shared artifact/provenance model:
+
+- **Artifacts**: Captured content with digests and metadata
+- **Evidence Anchors**: Pointers back to artifact locations (JSON Pointer, selector, line span)
+- **Provenance**: prov-spec records documenting capture and analysis
+
+## WCAG Rules (v0.1)
+
+| Rule | Finding ID | WCAG | Description |
+|------|-----------|------|-------------|
+| `lang` | `a11y.lang.missing` | 3.1.1 | Missing lang attribute on html element |
+| `alt` | `a11y.img.missing_alt` | 1.1.1 | Missing alt attribute on img element |
+| `button-name` | `a11y.button.missing_name` | 4.1.2 | Button without accessible name |
+| `link-name` | `a11y.link.missing_name` | 4.1.2 | Link without accessible name |
+| `label` | `a11y.input.missing_label` | 1.3.1 | Form input without label |
+
+## Related
+
+- [prov-spec](https://github.com/mcp-tool-shop/prov-spec) - Provenance specification
+- [a11y-evidence-engine](https://github.com/mcp-tool-shop/a11y-evidence-engine) - CLI scanner
+- [a11y-assist](https://github.com/mcp-tool-shop/a11y-assist) - Fix advisor
+- [a11y-demo-site](https://github.com/mcp-tool-shop/a11y-demo-site) - Demo with CI workflows
+
+## License
+
+MIT