A11y Fixes

---
name: a11y-fixes
description: Resolve axe-core accessibility violations reported by Vitest (test/a11y.ts), Playwright (.playwright/a11y.ts), or the code-review-audit agent's a11y bucket. Use when fixing violations like color-contrast, label, label-title-only, image-alt, button-name, link-name, region, landmark-one-main, heading-order, aria-allowed-attr, aria-required-attr, aria-required-children, aria-required-parent, aria-valid-attr-value, focus-trap, tabindex, html-has-lang, document-title, duplicate-id, listitem, definition-list. Trigger on any axe rule id appearing in test output.
model: haiku
---

# Accessibility Fix Patterns

How to resolve specific axe-core violations in this project.

Violations come from `test/a11y.ts` (Vitest), `.playwright/a11y.ts` (Playwright), or the `code-review-audit` agent's a11y bucket. General a11y guidance lives in `.claude/rules/accessibility.md`.

## color-contrast

WCAG AA requires 4.5:1 for normal text, 3:1 for large text. Use the project's semantic Tailwind tokens (see `.claude/rules/tailwind.md`) instead of arbitrary palette colors — they pair light/dark modes correctly.

```tsx
// BAD — fails contrast in dark mode, raw colors
<p className="text-gray-400 bg-white">Status</p>

// GOOD — semantic tokens, contrast-safe in both modes
<p className="text-body bg-body">Status</p>
```

## label

Form inputs need an associated `<label>`. Use GAIA's `Field` wrapper from `~/components/Form/Field` rather than a bare `<label>` — it wires `htmlFor`, error text, and description automatically. See the `form-components.md` audit extension.

```tsx
// BAD — bare input with no label association
<input type="text" name="email" />

// GOOD — Field wraps a project input with the right wiring
<Field type="input" name="email" label={t('email')}>
  <InputText name="email" />
</Field>
```

## label-title-only

`title` attributes are not labels — screen readers and mobile devices ignore them. Use `aria-label` or a real `<label>`.

```tsx
// BAD — title is not an accessible name
<input type="text" title="Search" />

// GOOD — aria-label provides the accessible name
<input type="text" aria-label={t('search')} />
```

## image-alt

Every `<img>` needs `alt`. Content images describe the image; decorative images use `alt=""`. See `.claude/rules/accessibility.md`.

```tsx
// BAD — no alt attribute
<img src="/logo.png" />

// GOOD — content image
<img src="/logo.png" alt={t('companyLogo')} />

// GOOD — decorative image, hidden from AT
<img src="/divider.svg" alt="" />
```

## button-name

Buttons need an accessible name. Visible text is fine; icon-only buttons need `aria-label`.

```tsx
// BAD — icon-only button with no name
<button onClick={onClose}>
  <CloseIcon />
</button>

// GOOD — aria-label supplies the name
<button aria-label={t('close')} onClick={onClose}>
  <CloseIcon />
</button>

// GOOD — visible text, no aria-label needed
<button onClick={onSave}>{t('save')}</button>
```

## link-name

Same pattern as `button-name` — anchors need an accessible name.

```tsx
// BAD — icon-only link
<Link to="/settings"><GearIcon /></Link>

// GOOD — aria-label on the link
<Link to="/settings" aria-label={t('settings')}>
  <GearIcon />
</Link>
```

## region / landmark-one-main

Page content must live inside a landmark, and there must be exactly one `<main>`. GAIA's Layout component owns the `<main>` landmark — page components render inside it and should not add their own.

```tsx
// BAD — page component wraps itself in <main>, duplicating Layout's
const Page = () => (
  <main>
    <h1>{t('title')}</h1>
  </main>
);

// GOOD — page renders into Layout's <main>
const Page = () => (
  <>
    <h1>{t('title')}</h1>
  </>
);
```

## heading-order

One `<h1>` per page. Levels do not skip — `h2 → h4` is a violation.

```tsx
// BAD — skips h3
<h2>{t('section')}</h2>
<h4>{t('subsection')}</h4>

// GOOD — sequential levels
<h2>{t('section')}</h2>
<h3>{t('subsection')}</h3>
```

## aria-allowed-attr

ARIA attributes are role-scoped. Look up the role; only attrs in its allowed list are valid. Common case: `aria-checked` only on `role="checkbox"`, `role="radio"`, `role="menuitemcheckbox"`, `role="menuitemradio"`, `role="switch"`, `role="treeitem"`.

```tsx
// BAD — aria-checked is not allowed on a button
<button aria-checked={selected}>{t('toggle')}</button>

// GOOD — aria-pressed for buttons, aria-checked for checkbox role
<button aria-pressed={selected}>{t('toggle')}</button>
```

## aria-required-attr

Some roles require companion attrs. Disclosure widgets (`aria-expanded`) need `aria-controls` pointing at the controlled element's id.

```tsx
// BAD — aria-expanded with no aria-controls
<button aria-expanded={open}>{t('menu')}</button>

// GOOD — aria-controls names the panel
<button aria-expanded={open} aria-controls="menu-panel">
  {t('menu')}
</button>
<div id="menu-panel" hidden={!open}>...</div>
```

## aria-required-children / aria-required-parent

Composite roles need their child roles, and child roles need the right parent. Prefer semantic HTML (`<ul><li>`, `<select><option>`) over recreating these structures with ARIA.

```tsx
// BAD — role="listbox" with no role="option" children
<div role="listbox">
  <div>{t('one')}</div>
  <div>{t('two')}</div>
</div>

// GOOD — semantic <select> with <option> children
<select aria-label={t('choose')}>
  <option value="1">{t('one')}</option>
  <option value="2">{t('two')}</option>
</select>
```

## aria-valid-attr-value

`aria-*` attrs that take id refs must point at existing ids; boolean attrs take `true`/`false`, not arbitrary strings.

```tsx
// BAD — aria-labelledby points at id that does not exist
<input aria-labelledby="missing-id" />

// GOOD — id exists in the DOM
<>
  <span id="email-label">{t('email')}</span>
  <input aria-labelledby="email-label" />
</>
```

## focus-trap (focus management)

Modals must trap focus while open and return focus to the trigger on close. See `.claude/rules/accessibility.md`. Prefer a vetted dialog primitive (Radix, react-aria) over hand-rolled focus logic.

```tsx
// BAD — open modal leaves focus on body, close drops focus
{
  open && (
    <div role="dialog">
      <button onClick={() => setOpen(false)}>{t('close')}</button>
    </div>
  );
}

// GOOD — primitive handles focus trap + restore
<Dialog open={open} onOpenChange={setOpen}>
  <Dialog.Content>
    <Dialog.Close>{t('close')}</Dialog.Close>
  </Dialog.Content>
</Dialog>;
```

## tabindex

Positive `tabindex` (`tabindex={1}`, `tabindex={2}`, ...) reorders the tab sequence and is always a violation. Use `tabIndex={0}` to insert into natural order, `tabIndex={-1}` for programmatic-only focus.

```tsx
// BAD — positive tabindex skews tab order
<div tabIndex={1}>{t('first')}</div>
<div tabIndex={2}>{t('second')}</div>

// GOOD — natural DOM order, programmatic focus on the panel
<div tabIndex={0}>{t('first')}</div>
<div tabIndex={0}>{t('second')}</div>
<section tabIndex={-1} ref={panelRef}>...</section>
```

## html-has-lang

`<html>` must have a `lang` attribute. The React Router root sets it from the i18n locale; if a violation appears, the root loader is not threading locale through. Verify the root layout reads locale from the request context and renders `<html lang={locale}>`.

```tsx
// BAD — hardcoded or missing lang
<html>...</html>

// GOOD — locale from the loader / i18n
<html lang={locale}>...</html>
```

## document-title

Every route needs a `<title>`. Set it via the route's `meta` export, and pull the string from i18n using the loader's `getInstance(context)` pattern (see `.claude/rules/i18n.md`).

```ts
// BAD — no meta, or hardcoded title
export const meta = () => [{title: 'Dashboard'}];

// GOOD — i18n-resolved title in the loader
export const loader = ({context}) => {
  const i18next = getInstance(context as RouterContextProvider);
  return {title: i18next.t('dashboard.meta.title', {ns: 'pages'})};
};
export const meta = ({data}) => [{title: data.title}];
```

## duplicate-id

Every `id` in the rendered DOM must be unique. Common Conform pitfall: rendering the same field `name` twice in a fieldset produces duplicate ids. Pass an explicit unique `id`.

```tsx
// BAD — same field rendered twice, ids collide
<InputText name="email" />
<InputText name="email" />

// GOOD — unique ids
<InputText id="email-primary" name="emailPrimary" />
<InputText id="email-secondary" name="emailSecondary" />
```

## listitem

`<li>` must be a direct child of `<ul>` or `<ol>`. A standalone `<li>` is a violation.

```tsx
// BAD — <li> with no list parent
<div>
  <li>{t('one')}</li>
</div>

// GOOD — wrapped in <ul>
<ul>
  <li>{t('one')}</li>
</ul>
```

## definition-list

`<dt>` and `<dd>` must live inside `<dl>`. Group related term/description pairs in one `<dl>`.

```tsx
// BAD — dt/dd outside <dl>
<div>
  <dt>{t('term')}</dt>
  <dd>{t('definition')}</dd>
</div>

// GOOD — wrapped in <dl>
<dl>
  <dt>{t('term')}</dt>
  <dd>{t('definition')}</dd>
</dl>
```