skills.rest
Tamtitam
TamtitamCOMMUNITY
Explore all skills by this author →
GitHub

aria-accessibility-fixer

Review and correct ARIA attributes in frontend HTML for WCAG compliance.

Updated Jan 7, 2026
Search Tags:#code review#html#accessibility#wcag#aria
One-click install
npx skills add https://github.com/Tamtitam/kakerlakk --skill aria-accessibility-fixer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aria-accessibility-fixer
Source: https://github.com/Tamtitam/kakerlakk/tree/main
Command: npx skills add https://github.com/Tamtitam/kakerlakk --skill aria-accessibility-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the issue of suboptimal ARIA usage in frontend code, helping to enhance accessibility and compliance with WCAG standards.

Core Features & Use Cases

  • ARIA Validation: Identifies and corrects ARIA usage errors.
  • Semantic HTML: Promotes the use of native HTML elements over ARIA attributes.
  • Accessibility Checks: Validates the presence of necessary labels and roles for proper accessibility.

Quick Start

Use the aria-accessibility-fixer skill to scan and fix ARIA issues in your frontend repository.

Frequently Asked Questions about aria-accessibility-fixer

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

FAQPage Schema
How do I fix incorrect ARIA attributes in my HTML code?▼

To fix incorrect ARIA attributes in HTML code, scan your frontend repository to identify errors and apply corrections that align with WCAG accessibility standards. This ensures your ARIA roles and properties are valid.

When do I need to use semantic HTML instead of ARIA attributes?▼

You need to use semantic HTML instead of ARIA attributes when native HTML elements can inherently provide the required accessibility features. Prioritizing semantic HTML ensures robust accessibility and reduces the risk of incorrect ARIA implementations.

How do I check my frontend code for missing ARIA labels and roles?▼

To check frontend code for missing ARIA labels and roles, analyze your HTML files to validate the presence of necessary accessibility properties. This ensures compliance with WCAG guidelines and corrects any missing attributes.

Does this ARIA validation process work with standard frontend repository files?▼

Yes, this ARIA validation process works with standard frontend repository files by analyzing your HTML and related code. It identifies suboptimal ARIA usage and enhances accessibility to meet WCAG compliance requirements.

What is the best way to meet WCAG accessibility standards in existing frontend code?▼

The best way to meet WCAG accessibility standards in existing frontend code is to run a comprehensive scan that identifies missing or incorrect ARIA attributes. It promotes semantic HTML and corrects accessibility errors.

Related Skills

Explore More Software Engineering Skills→
dragoscirjandragoscirjan

lang-html

Enforce semantic HTML, WCAG 2.1 AA accessibility, and keyboard navigability.

Community
Basic
nvimcraftnvimcraft

wcag-audit

Audit web interfaces for WCAG compliance and remediation requirements.

Community
Advanced
AGMO-IncAGMO-Inc
4

accessibility

Detect WCAG accessibility issues in React/HTML/CSS via static review.

Official
Intermediate
4lerman4lerman

a11y-audit

Scan web application code for WCAG 2.2 violations and suggest fixes.

Community
Advanced