modern-accessible-html-jsx

Generate semantic HTML and JSX code with accessible ARIA and labels.

Updated Jan 11, 2025
One-click install
npx skills add https://github.com/rdjakovic/todo2 --skill modern-accessible-html-jsx-rdjakovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modern-accessible-html-jsx
Source: https://github.com/rdjakovic/todo2/tree/main/.claude/skills/modern-accessible-html-jsx
Command: npx skills add https://github.com/rdjakovic/todo2 --skill modern-accessible-html-jsx-rdjakovic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that HTML and JSX code is written with a strong emphasis on semantic correctness and accessibility, preventing common pitfalls that hinder user experience and SEO.

Core Features & Use Cases

  • Semantic HTML: Promotes the use of meaningful HTML5 elements (header, nav, main, etc.) over generic div and span.
  • Accessibility Best Practices: Enforces keyboard accessibility, proper ARIA usage (or avoidance), and accessible naming conventions for interactive elements.
  • Form Accessibility: Guarantees that form labels are correctly associated with their controls and that validation feedback is accessible.
  • Image & Media Alt Text: Ensures all images have descriptive alt text or are marked as decorative.
  • Use Case: A developer can use this skill to review their JSX code for a new component, ensuring it's built with semantic elements and that all interactive parts are keyboard-navigable and properly labeled for screen readers.

Quick Start

Ensure the provided HTML snippet uses semantic elements and has accessible labels for all form inputs.

Frequently Asked Questions about modern-accessible-html-jsx

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

FAQPage Schema
How do I write semantic HTML and accessible JSX for web components?

To write accessible forms in JSX, you must explicitly associate form labels with their controls, ensure validation feedback is screen-reader accessible, and use proper ARIA attributes for interactive elements to maintain keyboard navigability.

What is the correct way to handle image alt text for web accessibility?

Form accessibility in JSX requires explicitly associating labels with their inputs, providing accessible validation feedback, and ensuring all interactive controls are keyboard-navigable and properly named for screen readers.

When should I use ARIA attributes versus semantic HTML elements?

You should prioritize semantic HTML5 elements like main and nav for structure, using ARIA attributes only when necessary to enhance keyboard accessibility and accessible naming for interactive components that cannot be achieved with native elements alone.

How do I ensure keyboard accessibility in frontend web development?

Keyboard accessibility is ensured by using semantic HTML elements, implementing proper ARIA roles, and guaranteeing all interactive parts of a component are navigable via keyboard without requiring a mouse, adhering to modern accessibility standards.

Does this accessibility approach work for standard HTML and JSX frameworks?

Yes, this accessibility approach applies to both standard HTML and JSX frameworks, enforcing semantic element usage, correct heading hierarchy, and accessible form label association across modern frontend web development environments.