Accessibility notes

Bashbox should feel playful without making the shopping path harder to use.

The public store, account tools, and kit instructions are designed toward an accessible baseline: readable copy, keyboard-friendly controls, clear focus states, reduced-motion alternatives, and practical activity notes for different needs.

Browse accessible kit notesRequest an accommodation
Digital
WCAG-minded
Store UI should keep contrast, focus, and forms usable.
Motion
Optional
Animated theme moments should respect reduced motion.
Activities
Adaptable
Kit notes can offer calmer, lower-mess, or mobility-aware options.
Store interface

The shopping path needs to stay readable, navigable, and predictable.

Bashbox can support expressive themes while keeping the shared commerce interface steady. The same parent may be comparing kits on a phone, navigating with a keyboard, using assistive technology, or trying to make a quick decision while managing a busy household.

Designed for scanning on mobile first, with enough detail on desktop for parents comparing order types, timing, and party fit.

Navigation
Keyboard access
Navigation menus, filters, kit cards, forms, account tools, and cart actions should remain usable without a mouse.
Focus
Visible focus
Interactive controls need clear focus states so users can tell where they are on the page.
Visual clarity
Readable contrast
Theme colors can add personality, but text, forms, prices, and calls to action should stay legible in light and dark mode.
Semantics
Named controls
Icon buttons, menus, filters, and custom controls should expose useful names, roles, and values to assistive technology.
Motion and themes

Theme animation should delight without becoming a requirement.

Bashbox themes can support animated space scenes, party transitions, and playful parallax, but purchasing and account tasks should never depend on motion. Reduced-motion preferences should turn decorative movement into static or simpler states.

Designed for scanning on mobile first, with enough detail on desktop for parents comparing order types, timing, and party fit.

User preference
Reduced-motion support
Decorative animation should respond to user motion preferences and avoid blocking key content.
Responsive UI
Stable layout
Images, carousels, filters, and cards need responsive constraints so content does not shift or overflow on mobile.
Clear signals
No color-only meaning
Status, pricing, availability, and warnings should use text and structure in addition to color.
Visual hierarchy
Readable theme layers
Theme art should support the page rather than sitting behind important text in a way that hurts legibility.
Activity notes

Inclusive parties need practical alternatives, not vague promises.

Activities should explain what a parent may need to adjust: noise, mess, mobility, reading level, sensory load, teamwork, and how much adult facilitation is required.

Designed for scanning on mobile first, with enough detail on desktop for parents comparing order types, timing, and party fit.

Sensory-aware
Sensory options
Kits can note quieter alternatives, lower-mess versions, and ways to reduce visual or tactile intensity.
Room fit
Mobility-aware setup
Setup cards can call out table height, floor space, reach, and whether activities work seated.
Age range
Mixed-age guidance
Activities can include simpler and more advanced roles so siblings and mixed-age groups can participate together.
Planning
Adult facilitation
Parents should know whether an activity is self-guided, lightly facilitated, or needs close adult help.
Questions

Accessibility questions

Bashbox accessibility work should be visible, specific, and easy to ask about.

Ask before checkout

A small detail can change whether a party activity feels welcoming.

Send the kit name, age range, setup space, and the adaptation you need so Bashbox can help choose or adjust the right pieces.

Request an accommodation