Skip to main content
rule CX Codex

accessibility · maxtrigify — Claude Code rule: what it does, how to install

accessibility is a Claude Code rule that enforces accessible frontend patterns. It triggers when generating UI components, dialogs, and navigation menus.

Apache-2.0 ★ 141 updated 2026-11-17

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/rules/accessibility.md
Open on GitHub

What accessibility does

The rule instructs the agent to select native HTML tags over generic containers, wire keyboard events, and declare ARIA attributes. It supplies ready-made structures for modals, tab lists, and dropdown menus.

It blocks aria-hidden="true" on interactive tags, insists on persistent form labels, and sets color contrast to 4.5:1. Touch targets for mobile layouts must meet the 44x44px boundary.

What it helps with

  • enforce native HTML elements over generic containers
  • handle keyboard navigation for menus and dialogs
  • attach accessible text labels to icon buttons and inputs
  • configure live regions for dynamic status updates

Example prompts for the agent

  • Build a dropdown menu with full keyboard controls and proper ARIA tags
  • Add accessible labels and error descriptions to this form
  • Audit this dialog component for WCAG compliance

How to install accessibility

Manually: put the files in place

.claude/rules/accessibility.md

The paths frontmatter field limits the files

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about accessibility

How to install accessibility in Claude Code?

Save the rule file to your project directory at .claude/rules/accessibility.md.

What does accessibility do?

It guides the assistant to follow WCAG guidelines, covering keyboard accessibility, focus indicators, semantic markup, and mobile touch targets.

What touch target size does accessibility enforce?

The guideline requires interactive mobile controls to be at least 44x44 pixels.

Source text

accessibility.md · Apache-2.0
---
title: Accessibility Guidelines
impact: CRITICAL
impactDescription: Essential for inclusive component design
tags: accessibility, a11y, aria, keyboard, screen-reader, focus, wcag
---

## Accessibility Guidelines

Accessibility (a11y) is not optional—it's a fundamental requirement. Every component must be usable by everyone, including people with visual, motor, auditory, or cognitive disabilities.

### Core Principles

#### 1. Semantic HTML First

Always start with the most appropriate HTML element:

**Incorrect (generic div):**

```tsx
<div onClick={handleClick} className="button">
  Click me
</div>
```

**Correct (semantic element):**

```tsx
<button onClick={handleClick}>Click me</button>
```

#### 2. Keyboard Navigation

Every interactive element must be keyboard accessible:

```tsx
function Menu() {
  const handleKeyDown = (e: React.KeyboardEvent) => {
    switch (e.key) {
      case "ArrowDown":
        focusNextItem();
        break;
      case "ArrowUp":
        focusPreviousItem();
        break;
      case "Home":
        focusFirstItem();
        break;
      case "End":
        focusLastItem();
        break;
      case "Escape":
        closeMenu();
        break;
    }
  };
  return (
    <div role="menu" onKeyDown={handleKeyDown}>
      {/* items */}
    </div>
  );
}
```

#### 3. Screen Reader Support

Use ARIA attributes when necessary:

```tsx
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/" aria-current="page">Home</a></li>
  </ul>
</nav>

<div aria-live="polite" aria-atomic="true">
  {isLoading && <span>Loading results...</span>}
</div>
```

#### 4. Visual Accessibility

Support users with visual impairments:

```css
/* Visible focus indicators */
button:focus-visible {
  outline: 2px solid var(--color-focus);
  outline-offset: 2px;
}

/* Sufficient color contrast (4.5:1 for normal text) */
.text {
  color: #333;
  background: white;
}
```

### ARIA Rules

1. **Don't use ARIA if you can use semantic HTML**
2. **Don't change native semantics unless necessary**
3. **All interactive elements must be keyboard accessible**
4. **Don't hide focusable elements** - Never use `aria-hidden="true"` on focusable elements
5. **All interactive elements must have accessible names**

### Component Patterns

#### Modal/Dialog

```tsx
function Modal({ isOpen, onClose, children }) {
  return isOpen ? (
    <div role="dialog" aria-modal="true" aria-labelledby="modal-title">
      <button onClick={onClose} aria-label="Close dialog">
        ×
      </button>
      {children}
    </div>
  ) : null;
}
```

#### Dropdown Menu

```tsx
<button
  aria-haspopup="true"
  aria-expanded={isOpen}
  aria-controls="dropdown-menu"
>
  Menu
</button>;
{
  isOpen && (
    <ul id="dropdown-menu" role="menu">
      <li role="menuitem" tabIndex={-1}>
        Item 1
      </li>
    </ul>
  );
}
```

#### Tabs

```tsx
<div role="tablist" aria-label="Tabs">
  <button role="tab" aria-selected={activeTab === 0} aria-controls="panel-0">Tab 1</button>
</div>
<div id="panel-0" role="tabpanel" aria-labelledby="tab-0">{/* content */}</div>
```

### Focus Management

```css
/* Show outline only for keyboard focus */
*:focus-visible {
  outline: 2px solid var(--color-focus);
  outline-offset: 2px;
}
```

### Live Regions

```tsx
// Polite announcement
<div role="status" aria-live="polite">{savedMessage && "Saved"}</div>

// Assertive announcement
<div role="alert" aria-live="assertive">{errorMessage}</div>
```

### Common Pitfalls

**Placeholder as labels:**

```tsx
// ❌ Placeholder disappears
<input placeholder="Email address" />

// ✅ Persistent label
<label>Email address <input type="email" /></label>
```

**Empty buttons:**

```tsx
// ❌ No accessible name
<button><TrashIcon /></button>

// ✅ Screen reader text
<button aria-label="Delete item"><TrashIcon aria-hidden="true" /></button>
```

**Disabled elements:**

```tsx
// ✅ Use aria-disabled and explain
<button
  aria-disabled={!isValid}
  aria-describedby="submit-help"
  onClick={isValid ? handleSubmit : undefined}
>Submit</button>
<span id="submit-help">{!isValid && 'Fill required fields'}</span>
```

### Mobile Accessibility

```css
/* Minimum 44x44px touch targets */
.button {
  min-height: 44px;
  min-width: 44px;
}
```

```html
<!-- Allow zooming -->
<meta name="viewport" content="width=device-width, initial-scale=1" />
```

© maxtrigify · Apache-2.0 · maxtrigify/Otto

Similar IDE rules

All IDE rules for Frontend and UI →

accessibility by other authors comes first.

accessibility Thientan Soparat Checks interactive elements against core accessibility requirements. Use it during UI audits or when completing a component. CX Codex +1 ★ 3,216repo stars tailwindcss-accessibility JosiahSiegel tailwindcss-accessibility is a Claude Code skill for building accessible interfaces with Tailwind CSS. It activates for WCAG work, focus styling, contrast, and ARIA patterns. CX Codex +1 302installs accessibility-auditor OneWave-AI accessibility-auditor audits web pages for accessibility defects and guides compliance with WCAG 2.1 AA. It runs automated checks, inspects keyboard navigation, and suggests markup fixes. CX Codex +1 346installs accessibility-a11y travisjneuman accessibility-a11y — a skill for Claude Code and Codex guides WCAG 2.2 compliance and interface accessibility checks. Activates during UI component development, accessibility reviews, or CI/CD test integration. CX Codex +1 161installs accessibility-wcag rohitg00 The accessibility-wcag skill for Claude Code provides WCAG 2.2 patterns for semantic HTML, ARIA dialogs, keyboard navigation, and color contrast. CX Codex +1 ★ 2,858repo stars accessibility-compliance aj-geddes The accessibility-compliance skill guides accessibility work for WCAG 2.1/2.2, keyboard navigation, screen readers and a11y checks in web interfaces. CX Codex +1 490installs better-accessibility jakubkrehel better-accessibility is a Claude Code skill that audits and fixes keyboard navigation, focus handling, forms, and ARIA markup against WCAG 2.2 standards. CX Codex +1 39,300installs

From the same set18

The whole set →
principles The principles rule for Claude Code establishes six core standards for component design. It guides agents during component creation, refactoring, and evaluation. CX Codex +1 ★ 141repo stars as-child as-child is a Claude Code rule for merging a component’s props and handlers into a custom child without an extra DOM wrapper. It applies to composable React triggers. CX Codex +1 ★ 141repo stars documentation documentation is a Claude Code rule that standardizes UI component documentation. It enforces consistent sections for props, runnable examples, and accessibility guidelines. CX Codex +1 ★ 141repo stars state state is a Claude Code rule for controlled and uncontrolled React component state. It applies while designing component APIs and state props. CX Codex +1 ★ 141repo stars polymorphism polymorphism is a Claude Code rule for React components that keep their styles and behavior across element types. The as prop selects the rendered element. CX Codex +1 ★ 141repo stars styling styling is a Claude Code rule that enforces Tailwind CSS patterns. Guides the agent to combine classes with tailwind-merge, clsx, and CVA. CX Codex +1 ★ 141repo stars definitions definitions is a Claude Code rule that classifies UI artifacts and keeps names consistent across primitives, components, blocks, templates, and patterns. CX Codex +1 ★ 141repo stars components-build components-build is a Claude Code skill for building, reviewing, and refactoring reusable React components with the components.build specification. It activates for work on component APIs, accessibility, styling, and TypeScript props. CX Codex +1 ★ 141repo stars

Project sponsors

Companies that keep this analytics open