Accessibility at CARA

• Partly supported

  Keyboard operation

  Every control is a native link, button, or form field, so Tab reaches it. In a scripted walk of the Products page, 39 of 40 Tab stops showed a focus indicator (the other was the end of the page's tab order, not a control) and Enter on a product row opened it.

  Evidence

  • captures/cara-a11y.spec.ts in the fleet screenshot harness: a Tab walk of the Products page and Enter on a product row, 11/03/2026
  • frontend/src/__tests__ in the CARA repo: Testing Library tests find every control by role and name, which only works for real, labeled controls
  • No one has walked every flow with a keyboard alone.

• Partly supported

  Screen reader landmarks and labels

  axe-core, which checks names, labels, roles, and landmark structure, found no serious or critical violations in any view. CARA has not been tested with a screen reader.

  Evidence

  • captures/cara-a11y.spec.ts runs axe-core on the Desk, Products, a product profile, a cited conversation, a conversation with no profile, and Settings, in light and dark at 1440 and 375 pixels
  • captures/cara.spec.ts fails a capture on a serious or critical axe-core violation in each captured state
  • Conversation replies are announced through a labeled live region (role log) and each message is a labeled article.

• Supported

  Contrast in light and dark

  Text and controls are checked for contrast in both the light and dark themes.

  Evidence

  • axe-core color-contrast rule on every view in both themes (captures/cara-a11y.spec.ts), no violations

• Not yet tested

  Reduced motion

  CARA's interface uses the Renkara design system's motion, which is designed to honor the reduced-motion setting. A scripted check found nothing animating on the Desk with or without the setting, but CARA's own tests do not exercise reduced motion.

• Not yet tested

  Text resize and zoom

  Resizing text to 200 percent has not been tested.

• Supported

  Mobile and touch

  Every view fits a 375 pixel and a 320 pixel wide screen with no sideways scrolling of the page; wide tables scroll inside their own labeled container. Most controls are 44 by 44 pixels or larger; inline citation numbers in a reply and the design system's brand link are smaller.

  Evidence

  • captures/cara-a11y.spec.ts: horizontal overflow of the page at 375 and 320 pixels on all six views, none
  • The same scan counts interactive targets under 44 pixels and lists them.

No WCAG conformance level is claimed for CARA. Its checks are automated and scripted only; no one has audited it against WCAG or tested it with a screen reader or other assistive technology.

• Structure

  A skip link, labeled landmarks (header, navigation, main, footer), one h1 per page, and headings that do not skip levels.

• Keyboard and focus

  Links and buttons are native elements, so they work from the keyboard. Focus is drawn as a visible ring, and the menu closes with Escape.

• Contrast

  Text meets 4.5 to 1 in both the light and dark themes, checked against the stylesheet by the test suite.

• Motion

  Transitions and animation switch off when your system asks for reduced motion.

• Small screens and zoom

  Layouts hold at 375 pixels wide with no sideways scrolling, text resizes with the browser, and touch targets are at least 44 pixels.

• Automated scan

  Every page is scanned with axe-core at 375 and 1440 pixels in light and dark, and the checks fail on any serious or critical violation. Automated tools find only part of the problems, so this is a floor, not proof.

• Images

  Every product screenshot has a text description and comes in a light and a dark version that follows your theme.

• Your theme choice

  The theme follows your system setting until you pick one with the button in the header.

Statement last reviewed 11/03/2026.