Sepia LabsLava Lampa Sepia Labs product

Accessibility

Last updated: 31 July 2026

We want everyone to be able to book an appointment, sign a document, buy a ticket, or run their business in Sepia — including people who use a screen reader, navigate by keyboard, rely on magnification, or need higher contrast.

Our target

We are working toward Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

We are not claiming that we currently meet that standard. We have not yet completed a full independent audit, and until we have, saying otherwise would be a promise we cannot back. This page describes what we have actually done, what we know is still missing, and how to reach a person if something blocks you.

What we have done

Accessibility is part of how the product is built rather than a pass at the end. In practice that currently means:

• Interactive controls are real buttons and links, so they are reachable and operable by keyboard.
• Icon-only controls carry text labels for screen readers.
• Forms use associated labels rather than placeholder text alone.
• Images that carry meaning have text alternatives.
• Status changes and loading states are announced rather than shown only as motion.
• Colour is not the only way we signal state — direction, icons, or text accompany it.
• Light and dark themes are both maintained, and text colour comes from theme variables rather than fixed values.

Known gaps

We would rather name these than let you discover them:

• No independent audit yet. Our checks so far have been internal. We have not had the product tested end-to-end by an accessibility specialist or by people who use assistive technology daily.
• Colour contrast has not been verified everywhere. Some surfaces — particularly the darker public pages for events and bookings — have not been measured against the AA contrast thresholds.
• Some editing tools assume a mouse. Drag-based interfaces, such as the email builder and the video timeline, are not currently operable by keyboard alone.
• Dense data tables are hard to navigate with a screen reader, and some controls appear only on hover.
• Uploaded images. Where a business using Sepia uploads its own photos, we cannot write the alt text for them. We are working on prompting for it at upload.

If something blocks you

Please tell us. You do not need to identify a WCAG criterion or use any particular language — describe what you were trying to do and what stopped you.

Email info@sepialabs.ai with “Accessibility” in the subject. We aim to reply within 5 business days.

If a barrier is stopping you from completing something time-sensitive — signing a document, paying an invoice, booking an appointment — say so, and we will find another way to get it done for you while we fix the underlying problem.

Pages run by other businesses

Businesses use Sepia to publish their own booking pages, event pages, forms and documents. We provide the underlying templates and are responsible for their accessibility. The content those businesses put into them — their wording, their images, their uploaded files — is theirs. If you hit a barrier on a page belonging to a business that uses Sepia, you can contact us and we will help, and we will pass on anything that is ours to fix.

How this page changes

We will update this statement as we complete an audit and close the gaps above, including the date it was last reviewed. If we ever claim conformance, it will be because testing supports it.

Contact

Sepia Labs LLC
3211 NW 7th Ave Cir
Miami, FL 33127
info@sepialabs.ai