Accessibility
Keep the interaction usable as you make it your own.
Keyboard and focus
Keep native buttons and links, accessible names, and visible focus styles. Try the Preview and Install tabs with the arrow keys, and check that dialogs close with Escape and return focus to their trigger. Controls such as the Precision dial offer keyboard and direct-value input alongside pointer interaction.
Motion preferences
Animated components check the device’s reduced-motion preference. Keep those checks when changing their timing or design, and provide a useful static appearance. Some effects also stop outside the viewport or in hidden tabs. Important status changes must remain understandable without animation.
Labels and visual alternatives
Give standalone icons and controls a meaningful accessible name; mark decorative artwork as decorative when adjacent text already explains it. Preserve status announcements and fallbacks. Check contrast after recoloring a component, and do not rely on color, sound, or hover alone to communicate an action.
Test your integration
Test keyboard navigation, a screen reader, increased text size, reduced motion, and a narrow touch screen in your own product. Accessibility depends on the surrounding interface and content; this collection is not a certification of your implementation. If you find a barrier in a Shipbits example, please report the component and steps so it can be investigated.