Skip to content

Accessibility.

Guests of every age and ability should be able to reply to an invitation. That is the bar.

Last updated 7 September 2026

What we aim for

We build toward WCAG 2.2 level AA across the marketing site, the wedding workspace, published wedding websites and the guest RSVP pages. In practice that means keyboard access to every control, visible focus, labelled form fields, readable contrast, text that scales, and captions or descriptions for images and video.

Where we are

The RSVP pages and the wedding workspace are built with server-rendered HTML and native form controls, which screen readers and keyboards handle well. Our marketing pages use real captures of the product with written descriptions. We have not yet completed a third-party audit, and some areas, in particular the drag-and-drop parts of the website and invitation editors, have keyboard alternatives that are still being improved.

Motion

Animations and autoplaying product recordings are turned off when your system asks for reduced motion.

Published wedding sites

Couples choose their own colours and fonts. Our palettes are built to keep text readable, and our templates use proper headings and alt text slots, but we cannot guarantee every combination a couple picks.

Tell us

If something is hard to use, write to us. Say which page, what device and browser, and what happened. We reply, and we fix what we can quickly.

Start with your guest list. Everything else follows.