Legal
Accessibility Statement
Last updated: June 1, 2026
Weddings are for everyone, and so is the software that plans them. Aisle Bliss is committed to building a product that works with assistive technology and meets WCAG 2.1 Level AA.
Standards we follow
We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the World Wide Web Consortium (W3C), and to comply with the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act.
What we do today
- Semantic HTML and ARIA labels on interactive elements
- Full keyboard navigation across all primary flows
- Color contrast of at least 4.5:1 for body text and 3:1 for large text
- Alt text on meaningful images and decorative alt="" on the rest
- Responsive layouts that scale to 200% zoom without loss of content
- Form fields with visible labels and accessible error messaging
- Skip links and landmark regions for screen reader navigation
- Reduced-motion support for users who prefer fewer animations
Known limitations
Some user-uploaded content, such as wedding photos and vendor portfolio images, may not always include alt text. We are building tooling that prompts vendors and couples to add descriptions at upload time.
Certain third-party embeds (maps, video players, payment forms) inherit the accessibility of the underlying provider and may not fully meet WCAG AA.
AI Concierge responses are generated by a language model. While we instruct the model to write in clear, plain language, output quality can vary.
Tell us when something is broken
If you hit an accessibility barrier on Aisle Bliss, please tell us so we can fix it. Use our accessibility report form and include the page URL, the assistive technology you are using, and a short description of the issue. We aim to respond within 5 business days and prioritize fixes that block core features.
Need information in another format?
If you need information from Aisle Bliss in large print, plain-text, or any other accessible format, email the address above and we will do our best to provide it.
Ongoing work
Accessibility is never finished. We run automated checks on every release, conduct manual audits with screen readers each quarter, and incorporate user feedback into our roadmap. For broader questions, see our DEI Policy.