modern-accessible-html-jsx

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

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Marioandres717/strength-ai --skill modern-accessible-html-jsx-marioandres717
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modern-accessible-html-jsx
Source: https://github.com/Marioandres717/strength-ai/tree/main/.claude/skills/modern-accessible-html-jsx
Command: npx skills add https://github.com/Marioandres717/strength-ai --skill modern-accessible-html-jsx-marioandres717

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that HTML and JSX code is accessible, semantic, and standards-compliant by default, helping teams avoid common accessibility defects and rework.

Core Features & Use Cases

  • Semantics-first markup using native elements (header, nav, main, section, article, footer) instead of generic divs.
  • Built-in accessibility guidelines for forms, images with meaningful alt text, and keyboard navigation.
  • Guidance for proper heading order, landmarks, and ARIA usage only when necessary to improve maintainability and accessibility.

Quick Start

Create accessible, semantic HTML/JSX structures by default, ensuring keyboard accessibility and proper semantics.

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 accessible HTML and JSX for screen readers and keyboard navigation?

To write accessible HTML and JSX, use semantics-first markup with native elements like header, nav, and main instead of generic divs, ensuring keyboard accessibility and meaningful alt text for images by default.

When should I use ARIA roles for accessible web components?

You should use ARIA roles only when necessary to supplement accessible web components. Prioritize native semantic HTML elements first to enforce landmark roles, proper heading order, and maintainable accessibility standards.

Does this accessibility approach work with both vanilla HTML and React JSX?

Yes, this accessibility approach works with both vanilla HTML and React JSX. It applies semantics-first structure, accessible form controls, and keyboard navigation guidelines across UI components, pages, and forms built in either format.

What is the best way to structure semantic HTML landmarks for web accessibility?

The best way to structure semantic HTML landmarks for web accessibility is replacing generic divs with native elements like header, nav, main, section, article, and footer to enforce standards-compliant structure by default.

How do I fix improper heading order and missing alt text in my JSX?

Fix improper heading order and missing alt text in JSX by enforcing semantics-first structure and built-in accessibility guidelines. This ensures proper heading hierarchy and meaningful image descriptions across your project.