Skip to Content
Design

Responsive and Accessibility

Keyboard, focus, touch, and mobile requirements for Qokit components and platform extensions.

Responsive and Accessibility

All public components and integration interfaces must support keyboard, touch, and varying language lengths simultaneously. Mobile layouts should be reorganized by task rather than simply shrinking the desktop interface.

Keyboard and Focus

  • Use semantic Button, Link, Label, Heading, Table, and List;
  • All interactions must be reachable and operable via keyboard;
  • Use shared focus-visible and --focus-ring; focus feedback must not be removed;
  • IconButton must provide localized aria-label;
  • Tooltip should only supplement information, not replace accessible names.

Touch and States

  • Compact control click areas must be no less than 40px; primary mobile operations must be no less than 44px;
  • Hover must not be the only indicator;
  • Disabled, Loading, Empty, and Error states must have understandable feedback;
  • Dangerous actions require clear copy and confirmation flows, not just reliance on red color.

Responsive Layout

  • Below tablet sizes, multi-column interfaces switch to single-column, collapsed, or drawer views based on task priority;
  • Header, Toolbar, tables, preview boxes, and action groups maintain stable dimensions;
  • Long labels, translated text, and user content must not overlap adjacent actions;
  • Both desktop and mobile must verify real content, focus order, and horizontal overflow.

Content and Contrast

  • Body text, descriptions, and CTAs remain readable on light, dark, and themed backgrounds;
  • Images must provide alt text consistent with their content;
  • Status must not be conveyed by color alone;
  • Animations respect prefers-reduced-motion; critical flows must not depend on animations to complete.

On this page