skills.rest
rakibulism
rakibulismCOMMUNITY
Explore all skills by this author →
Website𝕏@rakibulismGitHub

accessibility-auditor

Audit user interfaces for WCAG conformance and prioritized accessibility violations.

2|1|Updated May 17, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#wcag#contrast#ui audit
One-click install
npx skills add https://github.com/rakibulism/agent-skills-os --skill accessibility-auditor-rakibulism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/accessibility-auditor
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill accessibility-auditor-rakibulism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch accessibility barriers that make interfaces hard or impossible to use for people relying on keyboard navigation, screen readers, zoom, or touch input.

Core Features & Use Cases

  • WCAG Audits: Reviews a UI, page, or component against WCAG 2.1/2.2 AA or AAA targets.
  • Issue Prioritization: Ranks problems by severity so blockers, serious issues, and minor gaps are easy to triage.
  • Actionable Fixes: Explains each violation with the relevant success criterion, concrete remediation, and contrast guidance when needed.
  • Use Case: A designer shares a checkout flow screenshot and you return a prioritized accessibility review with specific fixes for focus order, labels, contrast, and semantics.

Quick Start

Audit the provided UI for WCAG 2.1 AA issues and return prioritized findings with fixes.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I run a WCAG audit on a UI screenshot?▼

To run a WCAG audit on a UI screenshot, provide the image to review the interface against WCAG 2.1/2.2 AA or AAA targets, returning prioritized violations with severity and concrete fixes.

What is the best way to check HTML or JSX for accessibility barriers?▼

Checking HTML or JSX for accessibility barriers involves auditing the code against WCAG criteria to identify keyboard, screen reader, and contrast issues, producing a prioritized list of violations with actionable remediation.

Can I audit keyboard navigation and screen reader support for my web components?▼

Yes, you can audit keyboard navigation and screen reader support by evaluating web components for WCAG conformance, which generates prioritized findings with specific semantic and focus order fixes.

Does this accessibility audit provide contrast guidance for low-vision users?▼

Yes, the accessibility audit provides contrast guidance for low-vision users by flagging color contrast violations and including specific remediation steps within the prioritized review output.

How are accessibility violations prioritized during the UI review?▼

Accessibility violations are prioritized by severity during the UI review, ranking blockers, serious issues, and minor gaps to make triage easy and clarify the most critical remediation steps.

What input formats work for automated WCAG conformance testing?▼

Accepted input formats for WCAG conformance testing include screenshots, HTML, JSX, and URL-described pages or components, allowing seamless integration into design review and development workflows.

Related Skills

Explore More Design & Creative Skills→
Marioandres717Marioandres717

modern-accessible-html-jsx

Improves HTML/JSX accessibility and semantic correctness for UI components, pages, and forms.

Community
Intermediate
SheTieJunSheTieJun
8

android-accessibility

Audit Jetpack Compose UIs for accessibility gaps and remediation steps.

Community
Advanced
wildbitcawildbitca
1

common-accessibility

Apply WCAG 2.2 and ARIA practices to UI components.

Official
Intermediate
hiyenwonghiyenwong
2

accessibility-wcag

Audit web interfaces for WCAG 2.2 conformance and provide remediation guidance.

Community
Advanced