skills.rest
artsmc
artsmcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-specialist

Identify and remediate web accessibility issues for WCAG 2.1 AA compliance.

Updated Mar 1, 2026
Search Tags:#accessibility#a11y#wcag#screen-reader#aria#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/artsmc/codex-agentic --skill accessibility-specialist-artsmc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-specialist
Source: https://github.com/artsmc/codex-agentic/tree/main/skills/accessibility-specialist
Command: npx skills add https://github.com/artsmc/codex-agentic --skill accessibility-specialist-artsmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams identify and remediate accessibility barriers to ensure WCAG compliance and usable interfaces for people with disabilities.

Core Features & Use Cases

  • WCAG compliance evaluation, remediation guidance, and ongoing accessibility posture.
  • Screen reader compatibility checks and keyboard-navigation improvements, including ARIA best practices.
  • Use Case: Auditing new web apps during development and performing accessibility remediation during QA.

Quick Start

Audit a web page for accessibility issues and deliver a prioritized remediation plan.

Frequently Asked Questions about accessibility-specialist

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

FAQPage Schema
How do I audit a web page for WCAG 2.1 AA compliance?▼

To audit a web page for WCAG compliance, you can use automated tools like axe-core, Lighthouse, or Pa11y alongside manual screen reader validation to identify accessibility issues and generate a prioritized remediation plan.

What is the best way to check screen reader compatibility and ARIA usage?▼

Checking screen reader compatibility involves validating proper ARIA usage and keyboard navigation to ensure interactive elements are accessible. Manual screen reader testing confirms that dynamic web interfaces are usable for people with disabilities.

How do I fix keyboard navigation issues during accessibility remediation?▼

Fixing keyboard navigation issues requires evaluating focus management and ARIA best practices during QA. Remediation ensures all interactive elements are operable without a mouse, meeting WCAG 2.1 AA keyboard accessibility requirements.

Does this approach support automated accessibility testing with axe-core and Pa11y?▼

Yes, this approach supports automated accessibility testing using axe-core, Lighthouse, and Pa11y. These tools identify common WCAG violations quickly, which are then validated through manual screen reader testing for comprehensive coverage.

What is inclusive design and when do I need an accessibility audit?▼

Inclusive design ensures web interfaces are usable by people with disabilities. You need an accessibility audit during development and QA phases to identify barriers, verify WCAG 2.1 AA compliance, and guide remediation efforts.

Why does my web app fail Lighthouse accessibility scores despite using ARIA?▼

Failing Lighthouse accessibility scores despite using ARIA often indicates incorrect ARIA implementation or missing keyboard navigation support. Auditing with axe-core and manual screen reader validation identifies specific WCAG compliance gaps for remediation.

Related Skills

Explore More Design & Creative Skills→
DexploarerDexploarer
6

wcag-compliance-checker

Audits web applications for WCAG 21 Level AA conformance using axe-core, pa11y, Lighthouse, and outputs remediation recommendations.

Community
Advanced
anavvanzinanavvanzin

agency-accessibility-auditor

Audit web and mobile interfaces for WCAG 2.2 accessibility barriers.

Community
Advanced
cosmixcosmix
53

accessibility

Audit web UI accessibility gaps with WCAG-aligned patterns for ARIA and keyboard navigation.

Community
Advanced
zinohomezinohome
1

accessibility-auditor

Audit web pages for WCAG 2.1 compliance and implement accessibility fixes.

Community
Advanced