Responsive Accessibility

Make Design Studio artifacts responsive, keyboard operable, semantically correct, and readable across common viewport and input conditions.

juspay 9f06514 1.1 KB Updated

File contents

Responsive and accessible UI

Treat mobile and accessibility as design inputs, not cleanup.

  • Start from content behavior: allow wrapping, use fluid widths, set sensible max-widths, and avoid fixed heights around text.
  • Add breakpoints only where the composition actually fails. Convert multi- column layouts into an intentional stacked order on narrow screens.
  • Use semantic headings in order, associated labels, button elements for actions, links for navigation, and helpful alternative text.
  • Ensure every interactive element is reachable and usable by keyboard.
  • Include visible :focus-visible, hover, active, disabled, and error states.
  • Respect prefers-reduced-motion and do not rely on hover for essential info.
  • Maintain WCAG AA-style contrast for normal text and important controls.

Validate at approximately 1440px, 1024px, 768px, and 390px widths. Check for horizontal overflow, clipped text, inaccessible menus, and reflow problems.

juspay/xyne-spaces/tree/main/apps/xyne-claw/design-skills/responsive-accessibility commit 9f06514f77

Frequently asked questions

npx skillmds@latest add juspay/responsive-accessibility