Skip to main content

Accessibility

A usable store is part of the product.

Curbidz is targeting WCAG 2.2 Level AA and equal access across browsing, customization, checkout, order status, policies, and support. This is a target—not a premature claim of full conformance.

Prelaunch draft

This page is a working draft, not a final policy or legal conclusion. Checkout is disabled until the missing business and product facts are finalized and the required review is complete.

Draft updated: August 30, 2026Conformance claim: none yetFeedback channel: pending verification

Our target

WCAG 2.2 Level AA

Curbidz is using the Web Content Accessibility Guidelines 2.2 Level AA as its technical target for the customer journey. The standard is maintained by the World Wide Web Consortium and is available in the official WCAG 2.2 recommendation.

Standards are a baseline, not the entire experience. Testing will include automated checks, keyboard-only use, screen-reader use, zoom and text resizing, reduced motion, color and contrast review, small screens, error recovery, and real completion of the personalized purchase path.

Built into these pages

Current accessibility foundations

The informational and draft-policy routes already include these structural features. They will be tested again when combined with the final global header and commerce experience.

Navigate clearly

  • A skip link to bypass repeated navigation
  • Semantic landmarks, headings, lists, and labeled navigation
  • Visible keyboard focus with no pointer-only interaction

Read comfortably

  • High-contrast core colors and legible text sizing
  • Layouts that reflow for narrow screens and enlarged text
  • Plain-language status and policy notices

Respect preferences

  • Reduced-motion behavior for users who request it
  • Print styling for policy review and recordkeeping
  • No essential information communicated by color alone

Customizer requirements

Personalization must work without sight or a mouse

Input and preview

  • Every control receives a persistent programmatic label.
  • Validation explains the problem in text and identifies the affected field.
  • Address digits and chosen options are available as text, not only as an image.
  • Updates are announced without stealing focus or producing constant noise.

Review and checkout

  • The final configuration is summarized in a logical reading order.
  • Price and policy changes do not occur only through color or animation.
  • Keyboard focus follows errors and return-from-payment states predictably.
  • Timeouts, if any, include warning and recovery appropriate to the risk.

Third parties

A hosted tool does not outsource responsibility

Parts of the intended experience may be provided by payment, email, security, monitoring, analytics, and shipping services. Curbidz will evaluate the customer-facing integrations it selects, configure them carefully, provide an accessible route into and back from them where possible, and maintain a support path when a barrier is reported.

An accessibility widget or automated score will not be treated as proof that the full journey works. Material barriers will be prioritized by impact, customer task, severity, and reach, with fixes verified rather than merely closed.

Feedback and alternatives

A monitored contact path comes before sales

Before checkout opens, this statement will publish a verified way to report an accessibility barrier or request information in another usable format. The process will ask for the page or task, a description of the barrier, and a preferred response method—not a diagnosis or proof of disability.

The final statement will identify the responsible seller, contact details, expected acknowledgment process, and escalation owner. Those facts are not invented here. Current channel status is available on the contact page.