ai_best_practices

Automate WCAP accessibility testing in Drupal development workflows with Playwright and axe-core.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mgifford/drupal-core --skill ai-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai_best_practices
Source: https://github.com/mgifford/drupal-core/tree/main/.agents/skills/ai_best_practices
Command: npx skills add https://github.com/mgifford/drupal-core --skill ai-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill consolidates best practices and structured workflows for integrating AI-powered accessibility testing into Drupal core development. It addresses the challenge of systematically identifying, evaluating, and fixing accessibility issues across multiple features and modules.

Core Features & Use Cases

  • Workflow Automation: Guides for automated testing using Playwright, axe-core, and custom scripts to ensure WCAG compliance.
  • Test Coverage Management: Organized test scenarios across critical, important, and extended functionalities, with detailed mapping to standards.
  • Impact Analysis: Frameworks for assessing accessibility regressions and improvements when enabling or modifying modules and patches.
  • Issue Tracking Integration: Schemes for consistent bug reporting with instance and pattern identifiers aligned with core schema.
  • Documentation & Planning: Templates and references for managing user stories, coverage matrices, and implementation queues.

Quick Start

Consult the documentation to integrate automated testing into your deployment pipeline, utilize the provided scripts for impact analysis, and follow the structured schemas to report issues effectively.

Frequently Asked Questions about ai_best_practices

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

FAQPage Schema
How do I automate WCAG compliance verification in a Drupal development workflow?

Automated WCAG compliance verification integrates Playwright and axe-core testing into your pipeline to evaluate accessibility regressions. This approach provides structured impact analysis frameworks and bug reporting schemas to systematically track violations across modules.

What is the best way to structure accessibility bug reporting for continuous integration?

Accessibility bug reporting requires consistent schemas using instance and pattern identifiers aligned with core standards. Structured documentation ensures systematic tracking of WCAG violations with stable identifiers, supporting continuous quality improvement in accessible design.

How does AI accessibility impact analysis work when enabling new Drupal modules?

AI accessibility impact analysis assesses regressions and improvements by running automated test scenarios across critical, important, and extended functionalities. It maps results to WCAG standards and provides frameworks to evaluate how patches and modules affect compliance.

Can I use Playwright and axe-core for automated accessibility testing across multiple modules?

Playwright and axe-core support automated accessibility testing across multiple modules through organized test scenarios. The framework provides detailed mapping to WCAG standards and custom scripts to ensure comprehensive coverage of critical, important, and extended functionalities.

What coverage matrices are needed for AI-assisted accessibility assessments?

AI-assisted accessibility assessments require organized test scenarios mapped across critical, important, and extended functionalities. Coverage matrices manage user stories and implementation queues, providing detailed mapping to WCAG standards for systematic violation tracking.

Why use structured identifiers for tracking WCAG violations in Drupal core development?

Structured identifiers for tracking WCAG violations ensure consistent bug reporting and systematic issue management across patches. Using stable instance and pattern identifiers aligned with core schema supports continuous quality improvement and prevents duplicate accessibility issue tracking.