skills.rest
rafifos
rafifosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fixing-accessibility

Audit HTML documents for accessibility issues and provide code-level fixes.

6|Updated Mar 24, 2019
Search Tags:#ui#accessibility#a11y#frontend#usability#aria#keyboard-navigation
One-click install
npx skills add https://github.com/rafifos/dotfiles --skill fixing-accessibility-rafifos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/rafifos/dotfiles/tree/main/dot_agents/skills/fixing-accessibility
Command: npx skills add https://github.com/rafifos/dotfiles --skill fixing-accessibility-rafifos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit HTML accessibility issues including ARIA labeling, keyboard navigation, focus management, color contrast, and form errors to ensure usable interfaces for all users.

Core Features & Use Cases

  • Audit and fix ARIA labeling across controls
  • Validate keyboard navigation and focus management
  • Check color contrast and form error messaging
  • Provide WCAG-compliant, accessible UI guidance for forms, dialogs, and interactive components

Quick Start

Audit a sample HTML page and implement the recommended accessibility fixes.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I audit HTML accessibility issues like ARIA labeling and keyboard navigation?▼

Audit HTML accessibility by analyzing ARIA roles, keyboard navigation, focus management, and semantic markup to generate concrete, code-level recommendations for interactive controls and forms.

What is the best way to fix color contrast and form error messaging for WCAG compliance?▼

Fix color contrast and form errors by validating UI components against WCAG standards, enforcing safe contrast ratios, and implementing descriptive error messaging with code-level guidance.

How do I ensure accessible naming and visible focus on interactive UI controls?▼

Ensure accessible naming and visible focus by auditing HTML elements for proper ARIA labels and enforcing visible focus states, providing specific markup corrections for dialogs and forms.

Does this accessibility audit work with standard HTML documents and frontend components?▼

Yes, this accessibility audit processes standard HTML documents to evaluate frontend usability, checking forms, dialogs, and interactive controls for WCAG compliance without requiring external dependencies.

Why does my frontend UI fail keyboard navigation and focus management tests?▼

Frontend UI fails keyboard navigation when HTML lacks proper semantic markup and ARIA attributes, requiring an accessibility audit to identify missing focus management and apply code-level fixes.

Can I check WCAG compliance for interactive dialogs and forms without external libraries?▼

Yes, you can check WCAG compliance for dialogs and forms by auditing raw HTML for ARIA labeling, focus management, and contrast issues, generating fixes without relying on external libraries.

Related Skills

Explore More Design & Creative Skills→
thec3ukthec3uk

Frontend Accessibility

Guide frontend code to meet accessibility standards like ARIA and keyboard navigation.

Official
Basic
CrazyDubyaCrazyDubya

accessibility-auditor

Audit web applications for WCAG 2.1 Level AA accessibility compliance.

Community
Intermediate
superpollo02superpollo02

artistic

Generates high-contrast UI component guidance with expressive typography and token-based color systems.

Community
Intermediate
vecearvecear

accessibility-auditor

Audit web applications for WCAG 2.1 accessibility issues.

Community
Advanced