Accessibility

The CRM Dashboard Kit is built with WCAG AA accessibility as a baseline. Every component and page meets or exceeds these standards, using semantic HTML, ARIA attributes, and accessible interaction patterns throughout all 35+ screens.

Every page includes a skip-to-content link as the first focusable element:

import { SkipLink } from "@/components/layout/skip-link"

<SkipLink />

The skip link is visually hidden until focused. It jumps the user directly to the #main-content landmark, bypassing the CRM sidebar and header navigation.

Color Contrast

All text meets WCAG AA contrast ratios:

Normal text (< 18px): minimum 4.5:1 contrast ratio
Large text (>= 18px bold or >= 24px): minimum 3:1 contrast ratio
UI components and states: minimum 3:1 against adjacent colors

The oklch color token system ensures contrast is maintained in both light and dark mode. The indigo/violet theme (hue 270) was specifically tuned so that primary-on-background and foreground-on-muted combinations pass AA thresholds.

All interactive elements are keyboard accessible:

Tab -- navigate between focusable elements in logical order
Shift+Tab -- navigate backwards
Enter/Space -- activate buttons, links, and toggles
Arrow keys -- navigate within menus, radio groups, tabs, and Kanban columns
Escape -- close dialogs, sheets, popovers, and the command palette

Focus Indicators

Visible focus rings appear on all interactive elements using the --ring design token:

:focus-visible {
  outline: 2px solid var(--ring);
  outline-offset: 2px;
}

Focus Traps

Focus is trapped inside overlay components to prevent keyboard users from tabbing behind them:

Dialog -- deal delete confirmation, contact merge dialog, import wizard modals
Sheet -- mobile sidebar navigation
Command -- global search command palette (Cmd+K)

When these components close, focus returns to the trigger element that opened them.

Semantic HTML

All pages use proper HTML5 landmarks:

<header> for the app header
<nav> with aria-label for sidebar navigation, mobile navigation, and pipeline stage tabs
<main> for primary content area
<aside> for the sidebar and detail panels
<section> with aria-label for dashboard widgets and report sections
<time> with datetime attribute for activity timestamps and deal dates

ARIA Labels

Icon-only buttons include descriptive labels:

<Button aria-label="Search contacts">
  <Search className="size-4" />
</Button>

<Button aria-label="Switch to dark mode">
  <Moon className="size-5" />
</Button>

Live Regions

The LiveRegion component announces dynamic content changes to screen readers:

import { LiveRegion } from "@/components/a11y/live-region"

<LiveRegion message="Deal moved to Negotiation stage" politeness="polite" />

Live regions are used for deal stage changes, contact save confirmations, task completions, and email send notifications.

Heading Hierarchy

Every page follows a strict heading hierarchy:

One <h1> per page (the page title)
<h2> for major sections
<h3> for subsections within those sections
No skipped heading levels

For example, the sales dashboard uses <h1> for "Dashboard", <h2> for "Revenue Overview", "Recent Deals", and "Activity Feed" sections, and <h3> within each section as needed.

Touch Targets

All interactive elements meet the 44x44px minimum touch target size. The kit includes a .touch-target utility class:

.touch-target {
  min-width: 44px;
  min-height: 44px;
}

This class is applied to icon buttons in the app header (search, notifications, user menu), sidebar navigation items, Kanban card actions, and pipeline stage controls on mobile.

Reduced Motion

The kit respects the prefers-reduced-motion media query. When enabled:

@media (prefers-reduced-motion: reduce) {
  *,
  *::before,
  *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}

This disables all animations including Kanban drag-and-drop transitions, chart entrance animations, sidebar collapse/expand transitions, notification slide-ins, shimmer loading states, and hover transforms on deal and contact cards.

Status Indicators

Status information is never conveyed by color alone. The kit uses color plus icon plus text:

{/* Deal stage uses icon + text + color */}
<TrendingUp className="size-3 text-chart-4" />
<span className="text-chart-4">+18% conversion</span>

{/* Overdue task uses icon + text + color */}
<AlertCircle className="size-3 text-destructive" />
<span className="text-destructive">Overdue</span>

The StageBadge and PriorityBadge components combine color-coded badges with readable text labels (Qualification, Proposal, Negotiation, Closed Won, etc.) so no information depends solely on color.

Form Accessibility

Forms across the kit follow accessibility best practices:

Labels associated with inputs via htmlFor/id
Error messages linked with aria-describedby
Required fields marked with visual indicators and aria-required
Invalid fields marked with aria-invalid for screen reader announcement
The contact create/edit forms, deal create/edit forms, settings forms, and email compose all follow these patterns
Zod validation errors are announced to screen readers when forms are submitted

Kanban Board Keyboard Accessibility

The deals pipeline Kanban board built with @hello-pangea/dnd supports full keyboard interaction:

Space -- lift and drop a deal card
Arrow keys -- move a lifted card between columns (left/right) or reorder within a column (up/down)
Escape -- cancel a drag operation and return the card to its original position

Each Kanban column includes an aria-label describing the stage name and deal count. Screen readers announce when a card is picked up, moved to a new stage, or dropped into position.

Testing Recommendations

Tool	Purpose
axe DevTools	Automated accessibility scanning
VoiceOver (macOS)	Screen reader testing
NVDA (Windows)	Screen reader testing
Keyboard-only navigation	Tab through every page
Lighthouse	Accessibility audit score

Skip Link