skills.rest
hmcts
hmctsOFFICIAL
Explore all skills by this author →
Website𝕏@HMCTSgovukGitHub

accessibility-check

Run axe-core accessibility checks on web UI components for WCAG 2.1 AA compliance.

3|4|Updated Apr 4, 2026
Search Tags:#a11y#web development#axe-core#accessibility check#WCAG 2.1 AA
One-click install
npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill accessibility-check-hmcts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-check
Source: https://github.com/hmcts/agentic-plugins-marketplace/tree/main/plugins/skills/accessibility-check/skills/accessibility-check
Command: npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill accessibility-check-hmcts

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ensures your UI components or pages are compliant with WCAG 2.1 AA standards by automatically running an a11y review using axe-core.

Core Features & Use Cases

  • Automated A11y Check: Run an accessibility check with axe-core for quick validation of WCAG 2.1 AA compliance.
  • Manual Checks Guide: Provides guidelines for additional manual checks for issues that automated tools can't capture.
  • Use Case: For developers ensuring accessibility of their web components and pages, to pass audits and comply with accessibility regulations.

Quick Start

Run 'accessibility-check' and follow the guidelines provided for manual checks if needed.

Frequently Asked Questions about accessibility-check

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

FAQPage Schema
How do I automate WCAG 2.1 AA accessibility checks for web components?▼

You can automate WCAG 2.1 AA accessibility checks by running axe-core against your web UI components to identify compliance issues automatically and flag non-automated findings for manual verification.

What accessibility issues can axe-core automatically identify?▼

axe-core automatically identifies web UI accessibility issues that comply with WCAG 2.1 AA standards, providing quick validation while flagging non-automated findings for additional manual checks.

Do I need to perform manual checks after an automated axe-core accessibility review?▼

Yes, you need to perform manual checks after an automated axe-core accessibility review to verify non-automated findings that automated tools cannot capture for full WCAG 2.1 AA compliance.

What is the best way to validate web page accessibility for WCAG 2.1 AA audits?▼

The best way to validate web page accessibility for WCAG 2.1 AA audits is running automated axe-core checks, followed by manual verification guidelines for issues automated tools cannot detect.

Why do automated accessibility checks miss WCAG 2.1 AA compliance issues?▼

Automated accessibility checks miss WCAG 2.1 AA compliance issues because certain non-automated findings require manual verification, as automated tools like axe-core cannot capture all accessibility nuances.

Related Skills

Explore More Software Engineering Skills→
tom-xstom-xs

accessibility-selenium-testing

Automate WCAG 2.1/2.2 accessibility audits with Selenium WebDriver and axe-core.

Community
Advanced
h4vzzh4vzz
33

Accessibility Testing

Audit web pages and components for WCAG 2.1 AA/AAA compliance.

Community
Advanced
SensLiaoSensLiao

qa-a11y-compliance

Scan web applications for WCAG 2.2 AA accessibility compliance.

Community
Advanced
emiljuchnikowskiemiljuchnikowski

a11y-audit

Integrate Playwright with axe-core to audit web pages for WCAG 2.1 AA violations.

Community
Intermediate