Accessibility and interaction

  • Use semantic headings, section, article, button, and form controls.
  • Every card action is a real button or link, not a click-only container.
  • Tab order follows: page heading → Add cluster → chooser/cards → card

actions.

  • Focus is visible on the split columns, buttons, fields, and cards' actions.
  • Minimum interactive target is 44 by 44 CSS pixels.
  • Use aria-describedby for endpoint field help and error text.
  • Announce status transitions such as Checking, Available, and Offline.
  • Do not rely on blue, green, or red alone to communicate status.
  • Respect reduced-motion preferences; no animated glow is required.