webability.io

WebAbility is a web accessibility platform — AI-powered widget, scanner, and agents for WCAG 2.2 / ADA / Section 508 / EAA compliance. https://webability.io This is **WebAbility MCP** (hosted Full). Free for everyone. Scan and check tools work with no account or key, under fair-use limits per IP. A free WebAbility account (sign-in prompted by your client) unlocks `visual_audit`, `start_audit` and `get_audit`. ## Engines used by scan_page - WebAbility detectors (60+ rules — gradient-aware contrast, weak names, decorative-icon detection, etc.) - axe-core (104 rules) - HTML_CodeSniffer (200+ rules) Results from all three are deduplicated into one issue list. ## Three-tier output (since v1.2.1, mirrors axe-core) `scan_page` and `flow_scan` return (`scan_html` is axe-only and returns raw violations): - **issues**: high-confidence violations — safe to act on - **incomplete**: needs human review — DO NOT auto-fix these. Common causes: contrast against gradient/image backgrounds, marketing-image alt text, framer-motion pre-animation states. - **summary**: counts by severity + an `incomplete` count When proposing fixes to the user, treat `incomplete` items as questions, not bugs. ## Structured fixes (since v1.6.0) Every issue carries `fix.op` from a closed set — `add-attribute`, `set-attribute`, `remove-attribute`, `add-element`, `remove-element`, `add-text-content`, `suggest` — plus `fix.attribute` / `fix.value` when known, and a top-level `fixability`: - **mechanical**: the value is known — apply it as given - **contextual**: the op is known, the VALUE needs judgment (alt text, a label) — read `html` and `message`, then write it - **visual**: needs rendered output (contrast, focus ring, target size) — propose, never auto-apply On React ≤18 / Vue dev builds each issue also carries `source` (`{file, line, column, component}`) read from the live component tree — open that file directly instead of calling find_source. Pass `sourceRoot` (local only) to get `sourceCandidates[]` for production builds. ## Output controls (every scan tool) `minImpact`, `rules[]`, `wcag[]` narrow the result; `format: "compact"` prints one line per element with rule metadata once — use it by default in a coding loop, it is a fraction of the tokens. ## Tool routing - "Scan this page / URL / localhost" → `scan_page` - "Walk through login → checkout" → `flow_scan` with `autoNavigate` - "What does this WCAG rule check" → `get_rules` - "Suggest a fix for this issue" → `detect_framework` then `generate_ai_fix` - "Did my fix work?" → `verify_fix` (after you edit the code AND serve the change — closes scan → fix → verify) - "What changed since the last scan / did I introduce regressions?" → `diff_scan` (baseline vs current → fixed / new / remaining) - "Check this contrast pair" → `check_color_contrast` (pass `url` to get brand-aligned suggestions) - "Find where this selector lives in code" → `find_source` (Lite / local only) - "Validate this HTML snippet / a component's markup" → `scan_html` (in-process, milliseconds, no browser — structural rules only; `engine: "browser"` for contrast) or `check_aria` - "Give me a shareable report of these findings" → `generate_report_pdf` (Lite / local only) - "Catch issues axe misses (icon contrast, focus visibility, look-but-not-button)" → `visual_audit` (free with account) - "I need a report to hand to a compliance officer / legal" → `start_audit`, then poll `get_audit` (free with account) - `find_source` / `scan_history` / `generate_report_pdf` are not available on the hosted server ## Important - The core loop: `scan_page` → `detect_framework` → `generate_ai_fix` → edit source → `verify_fix`. - Generated fix code edits the user's source — confirm before applying. - The widget runtime applies its own client-side patches at runtime; do not duplicate those edits in source code.