# Accessibility Fixer

> Turn WCAG 2.2 problems in your HTML into concrete code fixes, grouped by effort. Paste HTML or enter a URL and get a fix list: for every detected accessibility problem the tool shows the offending element, a corrected version generated from it (alt text, labels, lang, names, heading levels, table headers…) and how much work it is. Placeholders that need human judgement are marked TODO, and a patch-style diff is included.

Part of usefulweb.site (https://usefulweb.site/). Results are deterministic calculations from the inputs and the listed assumptions; the API returns exactly what the web page shows.

## Use it
- Human interface: https://accessibilityfixer.usefulweb.site/ (interactive tool at https://accessibilityfixer.usefulweb.site/tool)
- JSON API: POST https://accessibilityfixer.usefulweb.site/api/v1/calculate with a JSON object of inputs (schema: https://accessibilityfixer.usefulweb.site/api/v1/tool)
- OpenAPI: https://accessibilityfixer.usefulweb.site/openapi.json
- MCP (Streamable HTTP): https://accessibilityfixer.usefulweb.site/mcp - tool `accessibility_fixer`

## Inputs
- url (url): Page URL - Static HTML only; JavaScript is not executed.
- html (textarea): Or paste HTML - Takes precedence over the URL.
- includeBestPractice (boolean): Include best-practice and review items
- maxFixes (integer): Max fixes

## Method
- Runs the same static rule set as Accessibility Snapshot (WCAG 2.2 mapping verified against the W3C Recommendation).
- Each fix is generated from the actual element: the original start tag is re-serialised with the needed attribute added, changed or removed (e.g. alt, aria-label, lang, id + <label for>, th scope, tabindex).
- Text the tool cannot know — what an image shows, what a field means, the page language — is never guessed: it is inserted as a TODO placeholder (lang="en" is only a placeholder).
- Fixes are grouped by effort: quick = attribute change, moderate = markup change that may affect styling, involved = structural or content work.

## Limits
- Automated static checks can only detect some failures. They cannot establish WCAG 2.2 conformance: conformance requires a full manual review of every page state (WCAG 2.2 §5.2), including rendered contrast, keyboard operation and assistive-technology testing.