Accessibility Statement

Our commitment

Ammore is committed to making wedding planning usable by everyone, including people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard referenced by the Americans with Disabilities Act (ADA) and adopted by regulators and courts as the benchmark for accessible websites.

Accessibility is not a one-time project. We build it into our shared design system so that every screen inherits it, we test continuously, and we treat any barrier a person reports as a bug to be fixed.

What this covers

This statement applies to the Ammore web application at ammore.ai, including:

• The couple experience — sign-up, onboarding, dashboard, vendors, guests, timeline, hotels, music, and settings.
• The vendor experience — listing sign-up, claim, storefront, and leads.
• The guest-facing pages your wedding guests receive by text or link — RSVP, address collection, song requests, and shared timelines.

Measures we take

To meet WCAG 2.1 AA, we have implemented and continue to maintain:

• Semantic structure and landmarks (headings, navigation, and a main region) with a "Skip to content" link so keyboard users can bypass repeated navigation.
• Full keyboard operability — every interactive control can be reached and used without a mouse, dialogs trap and restore focus, and a visible focus indicator shows where you are.
• Programmatic labels on form fields, clear error messages announced to assistive technology, and required-field indication.
• Colour contrast that meets the AA thresholds for text and interface components, and status that is never conveyed by colour alone.
• Live announcements for dynamic updates such as saving, sending, and streaming assistant replies.
• Respect for the "reduce motion" system setting, which turns off non-essential animation.
• Text alternatives for images, icons, and data visualisations such as the budget breakdown.

How we test

We combine automated and manual testing: accessibility linting in the codebase, automated axe-core scans of our pages in continuous integration, keyboard-only walkthroughs, and screen-reader spot checks of our most-used flows. New features are checked before they ship.

Known limitations

We are transparent about areas still being improved:

• Some third-party components we embed — such as the Stripe payment form — are controlled by their providers; we choose accessible options and monitor them, but their conformance is ultimately theirs.
• A small number of rich, interactive widgets are still being refined against the full standard. If you hit a barrier anywhere, please tell us and we will prioritise a fix.

Conformance status

Ammore is substantially conformant with WCAG 2.1 Level AA: the platform meets the standard except for the limited, disclosed exceptions above, which we are actively remediating. A Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report describing our support for each success criterion is available on request.

Give us feedback

If you encounter any barrier using Ammore, or need information in a different format, please email support@ammore.ai. Tell us the page, what you were trying to do, and the assistive technology or browser you were using if you can. We aim to acknowledge accessibility reports within five business days and will work with you on a solution.

This statement will be updated as our accessibility work continues.