skills.rest
williamzujkowski
williamzujkowskiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Frontend Accessibility Validator

Run automated WCAG 2.2 accessibility checks with axe-core, Pa11y, and Lighthouse.

6|Updated Oct 25, 2025
Search Tags:#accessibility#a11y#wcag#automated-testing#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill frontend-accessibility-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Frontend Accessibility Validator
Source: https://github.com/williamzujkowski/cognitive-toolworks/tree/main/skills/frontend-accessibility-validator
Command: npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill frontend-accessibility-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures web applications meet WCAG 2.2 accessibility standards by identifying, reporting, and guiding remediation of accessibility issues across pages.

Core Features & Use Cases

  • Automated WCAG 2.2 validation using axe-core, Pa11y, and Lighthouse across multiple URLs.
  • ARIA, landmark, and semantic HTML analysis to ensure correct roles and structures.
  • Comprehensive remediation guidance including evidence, severity, and recommended fixes.
  • Use case: A development team rapidly audits a new web app for accessibility and prioritizes fixes by WCAG criteria.

Quick Start

Provide a list of URLs or HTML files to validate and I will run automated accessibility checks and return a comprehensive WCAG 2.2 report.

Frequently Asked Questions about Frontend Accessibility Validator

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

FAQPage Schema
How do I automate WCAG 2.2 accessibility checks across multiple web pages?▼

Automate WCAG 2.2 accessibility checks by providing URLs or HTML files to run axe-core, Pa11y, and Lighthouse, generating a structured compliance report with severity, evidence, and remediation guidance.

What is the best way to validate ARIA roles and semantic HTML for screen reader compatibility?▼

Validate ARIA roles and semantic HTML by running automated accessibility checks that analyze landmark structures and roles, returning evidence and recommended fixes to ensure screen reader compatibility.

Can I test keyboard navigation issues alongside automated WCAG compliance scans?▼

Yes, you can test keyboard navigation by enabling optional manual checks alongside automated axe-core, Pa11y, and Lighthouse scans, adding manual findings to the structured WCAG 2.2 compliance payload.

Does this accessibility validator work with local HTML files or only live URLs?▼

The accessibility validator works with both local HTML files and live URLs, running automated axe-core, Pa11y, and Lighthouse checks to return a comprehensive WCAG 2.2 compliance report.

What limitations exist when relying on automated WCAG 2.2 compliance testing?▼

Automated WCAG 2.2 testing covers ARIA and semantic HTML but may miss keyboard navigation and screen reader edge cases; optional manual checks are recommended to capture these manual findings and ensure full compliance.

Related Skills

Explore More Software Engineering Skills→
thiagoooo34252thiagoooo34252
1

engineer-accessibility

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

Community
Advanced
RB-chrismandichRB-chrismandich
1

a11y-audit

Audit web projects for WCAG 2.2 AA accessibility issues with ARIA and semantic HTML checks.

Community
Advanced
MolcajeteAIMolcajeteAI
2

accessibility-testing

Automate axe-core accessibility audits in Playwright and Vitest for React applications.

Official
Intermediate
SensLiaoSensLiao

qa-a11y-compliance

Scan web applications for WCAG 2.2 AA accessibility compliance.

Community
Advanced