webflow-mcp:accessibility-audit

Audits Webflow pages for WCAG 2.1 accessibility issues and applies attribute fixes.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/KryptaMedina7/quero-s-home --skill webflow-mcp-accessibility-audit-kryptamedina7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webflow-mcp:accessibility-audit
Source: https://github.com/KryptaMedina7/quero-s-home/tree/main/.agents/skills/accessibility-audit
Command: npx skills add https://github.com/KryptaMedina7/quero-s-home --skill webflow-mcp-accessibility-audit-kryptamedina7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Webflow pages often ship with accessibility barriers like unlabeled buttons, missing form labels, and removed focus outlines that block screen reader and keyboard users. This Skill scans any Webflow page headlessly via the Webflow MCP data tools, detects WCAG 2.1 violations, scores the page, and can apply fixes directly. ## Core Features & Use Cases - Headless WCAG 2.1 Audit: Extracts all page elements via data_element_tool and checks buttons, forms, links, headings, focus states, touch targets, and ARIA attributes without requiring a Designer connection. - Severity-Scored Reports: Categorizes findings as critical, serious, or moderate, calculates a 0-100 accessibility score, and generates formatted reports with element IDs, WCAG references, and concrete fixes. - Guided Auto-Fix Workflow: Presents a granular approval list and applies approved fixes using set_attributes, then reports the improved score. - Use Case: Before launching a marketing site, run a full-site audit across all 8 pages, discover that icon buttons lack labels site-wide, and fix them in one batch to raise the score from 64 to 90. ## Quick Start Run an accessibility audit on my Webflow homepage and list the critical issues with fixes.

Frequently Asked Questions about webflow-mcp:accessibility-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an accessibility audit on a Webflow page?

List your sites with data_sites_tool, pick a page from data_pages_tool, then extract elements with data_element_tool using get_all_elements. The audit checks buttons, forms, links, headings, and focus states, then produces a severity-scored report with fixes.

What accessibility issues does a WCAG 2.1 audit check in Webflow?

The audit checks icon-only buttons without labels, form inputs without labels, non-semantic click handlers, links without href, removed focus outlines, missing keyboard handlers, small touch targets, heading hierarchy skips, positive tabIndex, and incomplete ARIA roles.

Does the Webflow accessibility audit require a Designer connection?

No, the audit and fixes run headlessly against any page ID from list_pages using data_element_tool. A Designer connection is only needed if you optionally use element_snapshot_tool for visual previews of elements.

Can the audit fix accessibility issues automatically in Webflow?

Yes, after the report you approve individual fixes from a granular list, and the skill applies them with data_element_tool set_attributes in batches. It then reports successes, failures, and the improved accessibility score.

What are the limitations of automated Webflow accessibility audits?

The audit cannot check image alt text, color contrast, animation preferences, or actual screen reader behavior since it relies only on element attributes and structure. Manual testing with keyboard navigation and screen readers like NVDA or VoiceOver is still required.