Chairup
Accessibility Statement
Last reviewed May 30, 2026 · Version 2026-05-30-1
1. Our commitment
Chairup is committed to making our platform and the salon-facing pages we host usable by the widest possible audience, including people who use assistive technologies. We design and build to the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance Level AA as our internal target across both the Chairup platform (admin dashboard, signup, marketing site) and the tenant-facing booking, retail, and embed surfaces that we render on behalf of our customers.
2. What that means in practice
- Semantic HTML structure with a single primary
<main>landmark on every page and a “Skip to main content” link that is the first focusable element. lang="en"on the root<html>element so screen readers pronounce content in the correct language.- Visible
:focus-visibleoutlines on every interactive element (links, buttons, form fields), including buttons rendered inside Stripe Elements where supported. - Form inputs use programmatically associated
<label>elements (oraria-label/aria-labelledbywhere a visible label isn’t appropriate) and surface validation errors witharia-invalidandaria-describedby. - Color contrast meets WCAG 2.1 AA (4.5:1 for normal text, 3:1 for large text and UI components) in both light and dark themes.
- All motion respects the user’s
prefers-reduced-motionsetting; long-running animations and parallax effects are disabled when that preference is set. - Touch targets on mobile meet at least the 44×44 CSS-pixel minimum recommended by WCAG 2.5.5 (AAA).
- Keyboard navigation works throughout the platform: every action available with a pointer is reachable and operable from the keyboard alone, with logical tab order.
3. Tenant-facing pages
The booking pages, retail storefronts, embeds, and other end-customer surfaces we host on behalf of salons inherit the same component library, color tokens, focus styles, and semantic structure as the rest of the platform. Salons cannot disable these accessibility features through tenant settings. Salons remain responsible for the content they configure (service names, descriptions, photos, alt text on uploaded images, and any custom messages); we provide tooling and inline guidance to help them meet alt-text and plain-language standards.
4. Third-party components
Some surfaces incorporate third-party UI components — most notably Stripe Elements for card capture and Stripe Checkout for hosted payment pages. These components are maintained by Stripe and follow their own accessibility roadmap; we configure them to inherit our color tokens and focus styles where the API allows. If you encounter an accessibility issue inside an embedded Stripe surface, please report it to us as described below and we will escalate to Stripe as appropriate.
5. Known gaps
We test against WCAG 2.1 AA but we do not yet hold a third-party VPAT. Areas we are actively improving:
- Date-picker keyboard semantics on the mobile booking flow.
- Live-region announcements for asynchronous toast notifications.
- High-contrast review of dynamically generated tenant brand colors (we warn salons in the brand editor when a chosen accent fails AA contrast, but we do not currently block save).
6. Report an issue or request help
If you encounter content or functionality on the Chairup platform or on a salon’s tenant page that is not accessible to you, please email anthony@bluecollarlabs.org with the URL, a description of the issue, and the assistive technology you are using. We aim to respond to accessibility reports within five (5) business days and to fix confirmed issues as quickly as the change permits.
See also: Privacy Policy · Terms of Service.