Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Frontend Accessibility

  • 516 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

frontend-accessibility is a frontend skill that generates WCAG-compliant semantic HTML, ARIA labels, keyboard navigation, and screen reader optimizations for inclusive web applications.

About

frontend-accessibility is a skill from aj-geddes/useful-ai-prompts for building inclusive web UIs to WCAG standards. It guides implementation of semantic HTML structure, appropriate ARIA attributes, keyboard navigation patterns, and screen reader support so applications work for assistive technology users. Developers reach for frontend-accessibility when compliance is required, inclusive design is a release criterion, or existing components fail keyboard and screen reader checks. The skill includes quick-start guidance, reference guides, and best-practice checklists the agent applies while editing React, HTML, or component libraries. It fits frontend build tasks where accessibility must be designed into markup and interaction patterns, not patched after QA.

  • Implements WCAG compliance using semantic HTML and ARIA attributes
  • Ensures keyboard navigation and screen reader support
  • Automatically audits and fixes color contrast issues
  • Produces inclusive frontend components ready for production
  • Works across React, Vue, plain HTML, and Tailwind projects

Frontend Accessibility by the numbers

  • 516 all-time installs (skills.sh)
  • Ranked #581 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill frontend-accessibility

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs516
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you implement WCAG accessibility in React UI?

Generate WCAG-compliant semantic HTML, ARIA labels, keyboard navigation patterns, and screen reader optimizations directly in their frontend codebase.

Who is it for?

Frontend developers shipping inclusive web apps who need WCAG guidance applied directly in component code.

Skip if: Native mobile-only projects without web UI or teams needing formal third-party accessibility audit certification only.

When should I use this skill?

Building new UI components, fixing accessibility audit failures, or when compliance with WCAG and inclusive design is required.

What you get

Semantic HTML markup, ARIA labels, keyboard-navigable components, and screen-reader-optimized UI patterns.

  • accessible component markup
  • ARIA attribute map
  • keyboard interaction patterns

Files

SKILL.mdMarkdownGitHub ↗

Frontend Accessibility

Table of Contents

Overview

Build accessible web applications following WCAG guidelines with semantic HTML, ARIA attributes, keyboard navigation, and screen reader support for inclusive user experiences.

When to Use

  • Compliance with accessibility standards
  • Inclusive design requirements
  • Screen reader support
  • Keyboard navigation
  • Color contrast issues

Quick Start

Minimal working example:

<!-- Good semantic structure -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

<main>
  <article>
    <header>
      <h1>Article Title</h1>
      <time datetime="2024-01-15">January 15, 2024</time>
    </header>
    <p>Article content...</p>
  </article>

  <aside aria-label="Related articles">
    <h2>Related Articles</h2>
    <ul>
      <li><a href="/article1">Article 1</a></li>
      <li><a href="/article2">Article 2</a></li>
    </ul>
  </aside>
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Semantic HTML and ARIASemantic HTML and ARIA
Keyboard NavigationKeyboard Navigation
Color Contrast and Visual AccessibilityColor Contrast and Visual Accessibility
Screen Reader AnnouncementsScreen Reader Announcements
Accessibility TestingAccessibility Testing

Best Practices

✅ DO

  • Follow established patterns and conventions
  • Write clean, maintainable code
  • Add appropriate documentation
  • Test thoroughly before deploying

❌ DON'T

  • Skip testing or validation
  • Ignore error handling
  • Hard-code configuration values

Related skills

FAQ

What standards does frontend-accessibility follow?

frontend-accessibility follows WCAG guidelines using semantic HTML, ARIA attributes, keyboard navigation, and screen reader support so web applications meet inclusive design and compliance requirements.

When should frontend-accessibility be invoked?

frontend-accessibility should be invoked when building new UI, remediating audit failures, or meeting inclusive design requirements where components need keyboard access and assistive technology compatibility.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.