jahia-dev-accessibility

Audit Jahia JS modules for WCAG 2.1 AA violations with axe-core and Playwright.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Jahia/formidable --skill jahia-dev-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jahia-dev-accessibility
Source: https://github.com/Jahia/formidable/tree/main/.agents/skills/jahia-dev-accessibility
Command: npx skills add https://github.com/Jahia/formidable --skill jahia-dev-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies WCAG 2.1 AA accessibility violations in Jahia modules using axe-core and Playwright, enabling teams to quantify and fix accessibility issues before release.

Core Features & Use Cases

  • Automated live-page accessibility audits across all published pages.
  • Severity-based reporting with actionable fixes in React views and CSS.
  • Invoke after building components or before final review to ensure WCAG compliance.

Quick Start

Run the a11y audit workflow against your Jahia module to identify and fix WCAG violations.

Frequently Asked Questions about jahia-dev-accessibility

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

FAQPage Schema
How do I automate WCAG 2.1 AA audits for Jahia components?

Automate WCAG 2.1 AA audits for Jahia components by running axe-core and Playwright against live pages listed in a pages.json file. This workflow identifies accessibility violations and generates severity-based reports to guide fixes in React views and CSS.

What's the best way to fix axe-core accessibility violations in Jahia React views?

Fix axe-core accessibility violations in Jahia React views by running the audit workflow after building components. It reports violations by severity and provides actionable fixes directly within the React views and CSS to ensure WCAG compliance before release.

Do I need Playwright and axe-core to run accessibility checks on live Jahia pages?

Yes, you need Playwright and axe-core to run accessibility checks on live Jahia pages. The audit workflow also requires a live-page surface, specifically a pages.json listing, to target all published pages for automated WCAG violation detection.

When should I run an automated accessibility audit on my Jahia modules?

Run an automated accessibility audit on Jahia modules after building components or before final review. This timing ensures WCAG 2.1 AA compliance is verified against live pages and any React or CSS violations are fixed before release.

Does this accessibility audit report violations by severity?

Yes, the accessibility audit reports violations by severity. It leverages axe-core to scan live Jahia pages and outputs a severity-based report, enabling teams to quantify issues and apply targeted fixes to React views and CSS.

Can I use Playwright to check published Jahia pages for WCAG violations?

Yes, you can use Playwright combined with axe-core to check published Jahia pages for WCAG violations. The workflow requires a pages.json file listing the live pages to scan, ensuring all published content meets WCAG 2.1 AA standards.