Skip to main content
BoxNear← Back to app

Accessibility Statement

Version 1.1Effective: July 14, 2026Last updated: July 14, 2026

BoxNear is committed to making the marketplace usable by everyone, including people who rely on assistive technology. This statement describes our target conformance level, the measures in place, and how to report an accessibility barrier.

1. Conformance target

BoxNear targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA for the public marketplace, buyer flows, seller flows, and account management surfaces.

2. Measures we take

  • Semantic HTML with a single <main> landmark per route and hierarchical headings.
  • Design-system color tokens with contrast targets of 4.5:1 for body text and 3:1 for large text and interactive borders in both light and dark themes.
  • Accessible primitives from Radix UI (dialogs, menus, popovers, combobox) with keyboard navigation, focus management, and screen reader announcements.
  • Explicit aria-label on every icon-only button.
  • Form inputs paired with visible labels or programmatic labels.
  • Focus-visible outlines on all interactive elements.
  • Tap targets sized to a minimum of 44×44 CSS pixels on mobile primary actions.
  • Support for the browser's reduced-motion preference on non-essential animations.
  • lang="en" on the document root; dynamic status regions marked with aria-live.
  • Skip-to-content link at the top of every page for keyboard users.

3. Testing

Accessibility is checked with a combination of automated audits (axe-core), manual keyboard-only navigation, and screen reader spot checks. Automated audits are re-run whenever new user-facing routes ship. This statement reflects the most recent audit.

4. Known limitations

The following areas are known to have partial accessibility support and are on our remediation roadmap:

  • Interactive map — the Mapbox map surface uses drag-based pan and pinch-to-zoom; keyboard-only users can browse listings via the accessible listing list view rather than the map.
  • Camera-based Smart Scanner — the AI vision scanner requires a working camera. Sellers who cannot use a camera can enter listings manually through the standard listing form.
  • User-uploaded photos — sellers may not always provide descriptive text for listing photos. The listing title, description, condition, and pickup information carry the meaningful information about the item.
  • Third-party embedded flows — Stripe Connect onboarding and Stripe Elements are provided by Stripe; their accessibility is governed by Stripe.

5. Compatibility

BoxNear is designed to work with the latest two major versions of Chrome, Edge, Safari, and Firefox on desktop, and with Safari on iOS 16+ and Chrome on Android 12+. Screen readers tested include VoiceOver on iOS and macOS.

6. Feedback

If you encounter an accessibility barrier on BoxNear, or if you need content in an alternative format, please email support@boxnear.com. Include the URL of the page, the assistive technology you are using, and a description of the problem. We aim to respond within 5 business days.

7. Formal complaints

If you are not satisfied with our response, you may file a complaint with your local disability-rights authority.