accessibility-fundamentals

Identify and fix accessibility issues in JSX UI components using WCAG, ARIA, and keyboard navigation.

274|18|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/DanielPodolsky/ownyourcode --skill accessibility-fundamentals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-fundamentals
Source: https://github.com/DanielPodolsky/ownyourcode/tree/main/.claude/skills/fundamentals/accessibility
Command: npx skills add https://github.com/DanielPodolsky/ownyourcode --skill accessibility-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and fix accessibility issues in UI components by applying WCAG, ARIA, and keyboard navigation best practices. It guides teams to ensure interactive elements, forms, and dialogs are usable by all users, including those relying on assistive technologies.

Core Features & Use Cases

  • Accessibility auditing and guidance for WCAG, ARIA, and keyboard navigation across common UI elements (forms, buttons, modals, and interactive components).
  • Practical examples, checklists, and best-practice patterns that teams can apply during development and code reviews.
  • Use Case: When junior developers implement a login form, the skill helps ensure proper labels, focus management, and screen reader compatibility to deliver an inclusive experience.

Quick Start

Review a sample JSX form or modal to verify keyboard focus, proper labeling, and aria attributes; apply the provided checklists to fix issues and improve the component's accessibility.

Frequently Asked Questions about accessibility-fundamentals

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

FAQPage Schema
How do I fix accessibility issues in JSX forms and modals?

Fix accessibility issues in JSX forms and modals by applying semantic HTML, ARIA labeling, and focus management. This skill provides structured checklists and concrete examples to ensure interactive elements are usable with screen readers and keyboards.

What WCAG and ARIA best practices should I apply for screen reader compatibility?

For screen reader compatibility, apply WCAG and ARIA best practices by using proper semantic HTML elements, adding accurate ARIA attributes for labeling, and ensuring logical focus order. This skill guides these adjustments for inclusive interactive components.

How do I implement keyboard navigation for interactive UI elements?

Implement keyboard navigation by managing focus states and ensuring all interactive UI elements are operable without a mouse. This skill provides practical testing guidance and patterns to verify focus management across forms, buttons, and modals.

Do I need external tools to audit UI components for accessibility?

You do not need external tools to audit UI components for accessibility. This skill requires no external tools beyond a standard development environment, relying on structured checklists to identify and fix issues during development and code reviews.

What is the best way to ensure login forms are accessible for assistive technologies?

The best way to ensure login forms are accessible is to verify proper labels, manage keyboard focus, and add screen reader compatibility. This skill provides checklists to validate these elements and deliver an inclusive user experience.