rule-accessibility

Enforce WCAG 2.1 AA and Section 508 accessibility checks in frontend code.

1|1|Updated Mar 31, 2026

Search Tags:#testing #accessibility #a11y #frontend #wcag #aria #jest-axe

Ready to run

npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill rule-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-accessibility
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.claude/skills/rule-accessibility
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill rule-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern frontend projects require strict accessibility conformance to WCAG 2.1 AA and Section 508. This Skill provides enforceable guidelines and checks to ensure frontend code, ARIA labeling, and keyboard navigation meet federal requirements.

Core Features & Use Cases

Enforces ARIA labeling and accessible name requirements for interactive elements in frontend code.
Includes test guidance and examples for preventing common accessibility violations in components and forms.
Use Case: A development team runs automated accessibility checks in CI to catch violations before they reach review.

Quick Start

Run automated accessibility checks across frontend components and fix any violations before merging.

Frequently Asked Questions about rule-accessibility

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

FAQPage Schema

How do I enforce WCAG 2.1 AA compliance in frontend code?▼

Enforce WCAG 2.1 AA compliance by applying required accessibility practices to frontend code edits, ensuring proper ARIA labeling and keyboard navigation for interactive elements. This provides automated checks to catch violations before code review.

How do I test frontend components for accessibility violations using jest-axe?▼

Test frontend accessibility with jest-axe by running automated checks across components and forms to prevent common violations. This catches ARIA labeling and keyboard navigation issues in CI before they reach the review stage.

What ARIA labeling requirements are needed for Section 508 compliance?▼

Section 508 compliance requires accessible name requirements and proper ARIA labeling for all interactive elements in frontend code. This ensures keyboard navigation and frontend accessibility meet federal project standards.

Can I use automated accessibility checks to catch WCAG violations in CI?▼

Yes, you can run automated accessibility checks in CI to catch WCAG violations before merging. This enforces ARIA labeling and keyboard navigation standards across frontend components and forms during code edits.

Does this accessibility guidance work for federal projects requiring Section 508 compliance?▼

Yes, this accessibility guidance applies across frontend code edits, tests, and UI builds in federal projects. It enforces WCAG 2.1 AA and Section 508 compliance through ARIA labeling and jest-axe testing.

What keyboard navigation standards must interactive frontend elements meet?▼

Interactive frontend elements must meet WCAG 2.1 AA keyboard navigation standards with proper ARIA labeling and accessible names. This ensures all interactive components are operable without a mouse for accessibility compliance.