TechAccess
AI-powered accessibility toolkit. WCAG audits, code fix generation, alt text evaluation, and structured reports — powered by local AI.
Built by Like One Foundation — because accessibility shouldn't require a six-figure budget.
Install
pip install techaccess
playwright install chromium
CLI
# Full WCAG audit with score
techaccess audit https://example.com
# AI-enhanced audit (semantic analysis via Ollama)
techaccess audit https://example.com --ai
# Generate code fixes for accessibility issues
techaccess fix https://example.com
# Evaluate alt text quality
techaccess evaluate https://example.com
# ARIA accessibility tree snapshot
techaccess snapshot https://example.com
# Contrast ratio check
techaccess contrast https://example.com
Output Formats
# JSON, Markdown, SARIF (GitHub Code Scanning), or HTML report
techaccess audit https://example.com -f html -o report.html
techaccess audit https://example.com -f sarif -o results.sarif
# CI mode — exit code 1 on serious+ issues
techaccess audit https://example.com --fail-on serious
MCP Server
# Add to Claude
claude mcp add techaccess -- python /path/to/server.py
Tools: access_audit, access_fix, access_evaluate, access_snapshot, access_contrast, access_alttext
How It Works
TechAccess combines three layers:
- axe-core — industry-standard WCAG 2.0/2.1/2.2 rule engine
- Playwright ARIA — captures the full accessibility tree for semantic analysis
- AI layer — local models (Ollama) or Claude API for:
- Semantic ARIA analysis (landmark structure, heading hierarchy, focus order)
- Alt text generation and evaluation (llava for vision)
- Code remediation with before/after diffs
- Contextual fix suggestions
Scoring
0-100 score with letter grade (A+ through F). Weighted by severity: critical issues count 4x more than minor ones.
Reports
- JSON — machine-readable, CI/CD integration
- Markdown — human-readable summaries
- SARIF — GitHub Code Scanning compatible
- HTML — dark-themed dashboard with charts and fix previews
Requirements
- Python 3.10+
- Chromium (installed via Playwright)
- Optional: Ollama for local AI features
License
MIT. Free forever.
Metadata
Release files for techaccess 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| techaccess-0.3.1.tar.gz | 184.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| techaccess-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 361.3 kB
Release files / techaccess-0.3.1.tar.gz
| Download URL | techaccess-0.3.1.tar.gz |
|---|---|
| Size | 184.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72e6c86639d923a4f92c1f8ef028815adb7ef0df47f7b510f573dd9c3498d197
|
|
BLAKE2b-256 checksum How to use checksums |
640bb47e2877595c0d6ad1664c91be20c2cfbdd7cee59c350c6e96a370aa8a4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 9, 2026.
Transparency logRelease files / techaccess-0.3.1-py3-none-any.whl
| Download URL | techaccess-0.3.1-py3-none-any.whl |
|---|---|
| Size | 177.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5a5ccd98d785da7708e9d8b0b692c5ff077329aac9789065c00cb3d7c8c4abc
|
|
BLAKE2b-256 checksum How to use checksums |
e2b7383df46ad3c2e85ac8b1f82ca7950681c776a6635ab471a8c6c39380a98e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 9, 2026.
Transparency logSecurity for techaccess 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for techaccess-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.