skills.rest
wpgaurav
wpgauravCOMMUNITY
Explore all skills by this author →
Website𝕏@wpgauravGitHub

accessibility-audit

Audit Builderius templates for WCAG 2.2 accessibility issues and generate findings reports.

14|1|Updated Mar 30, 2026
Search Tags:#accessibility#a11y#audit#usability#wcag#builderius
One-click install
npx skills add https://github.com/wpgaurav/WordPress-skills --skill accessibility-audit-wpgaurav
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/wpgaurav/WordPress-skills/tree/main/skills/uncategorized/accessibility-audit
Command: npx skills add https://github.com/wpgaurav/WordPress-skills --skill accessibility-audit-wpgaurav

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool identifies and remediates WCAG 2.2 accessibility issues within Builderius templates, helping teams deliver inclusive, compliant user experiences.

Core Features & Use Cases

  • Automated landmark and heading hierarchy checks to verify semantic structure.
  • ARIA attribute audits, image alt text validation, and focus management assessment.
  • Troubleshooting guidance for collection loops, forms, and interactive components, with actionable remediation steps for builders.
  • Use Case: When auditing a Builderius template for a client site, run a full accessibility pass to surface issues like missing alt text, inappropriate landmark usage, or inaccessible navigation, then apply fixes with Builderius MCP tools.

Quick Start

Audit a Builderius template for WCAG 2.2 conformance and generate an accessibility remediation plan.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit Builderius templates for WCAG 2.2 compliance?▼

You audit Builderius templates for WCAG 2.2 compliance by inspecting modules, attributes, and structure via Builderius MCP Tools to identify landmark, heading, ARIA, and form issues, producing an accessibility findings report.

What is checked during a WCAG 2.2 accessibility audit on Builderius?▼

A WCAG 2.2 accessibility audit on Builderius checks semantic structure, landmark usage, heading hierarchy, image alt text validation, ARIA attributes, form accessibility, links, and focus management to ensure inclusive user experiences.

Do I need Builderius MCP Tools to run an accessibility audit?▼

Yes, you need Builderius MCP Tools to run this accessibility audit, as the workflow enforces using them to inspect template modules, attributes, and structure for generating the WCAG 2.2 remediation report.

Can I troubleshoot inaccessible collection loops and forms in Builderius?▼

Yes, you can troubleshoot inaccessible collection loops and forms in Builderius by auditing their interactive components and applying the actionable WCAG 2.2 remediation steps provided for builders.

What is the best way to remediate ARIA and focus management issues in Builderius?▼

The best way to remediate ARIA and focus management issues in Builderius is to audit attributes via MCP Tools, assess interactive components, and apply the generated actionable remediation steps to meet WCAG 2.2 standards.

Related Skills

Explore More Design & Creative Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
knckknckknckknck

wcag-audit-patterns

Audit WCAG 2.2 conformance with axe-core, pa11y, and lighthouse.

Community
Advanced
githubgithub
37.6k

mcp-cli

Execute MCP server tools with JSON payloads via CLI.

Official
Basic
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced