Accessibility statement

Vereli is built so that everyone can use it, including people who use a screen reader, navigate with a keyboard, or browse on a small screen. That applies to the public wedding pages, the couple's plan and registry, and the vendor pages and dashboard.

For couples and vendors, that means you should be able to find a vendor, plan, share a registry or manage a listing without needing a mouse or good eyesight. We are working towards the international standard for this, WCAG 2.2 Level AA, and we are not there everywhere yet. We would rather say that plainly than claim a standard we haven't fully checked. This page states what has actually been checked, what we already know still needs work, and how to tell us about a barrier we've missed.

What's been checked

Two internal review passes, 21 September 2026 (issues #1703, #1704), both since fixed. The method was our own checklist, not a formal standard or an outside process: we measured colour contrast with browser tooling, tried every page using only a keyboard, and measured touch targets at phone width, then checked what we found against the matching WCAG 2.2 AA criteria.

• Colour contrast. The muted text colour used for ledes, descriptions and helper text measured 4.06:1 on white, below the 4.5:1 AA floor for body text. It now maps to a darker token measuring 7.36:1.
• Keyboard and screen-reader navigation. No page had a skip link; the header navigation landmark had no accessible name on most pages; one page had no top-level heading. All three are fixed.
• Touch target size. As many as 43 interactive elements on one page (the directory, at 390px wide) measured under the 44×44px minimum: navigation links, filter chips, small text links and checkboxes. On the pages we re-measured at 390px wide, targets now meet that minimum. We have not re-measured every page.

A further internal pass on 14 October 2026 (issue #2750), keyboard and zoom only: using Tab alone we checked the tab order, focus visibility and field labels on the registry landing, sign-up, sample registry, directory and shop pages, and at 200% zoom none of them scrolled sideways. Each page has one main heading and one main area. It found one barrier, a missing skip-to-content link, which is now fixed.

What we know still needs work

• No independent or automated full-site audit has been done. The checks above were a manual internal review against specific known issues, not a systematic sweep against every WCAG 2.2 AA success criterion. We're getting a quote for one (recorded internally, not yet commissioned).
• No screen-reader testing, by us or by a real screen-reader user. Our own checks used browser tooling and keyboard-only navigation, not an actual assistive-technology user's experience. We have also not yet completed the RSVP and buy flows by keyboard alone.
• Signed-in and data-driven pages (the couple's plan and registry, the vendor dashboard) haven't had the same dedicated pass as the public marketing pages yet.

Tell us about a barrier

If something on Vereli is hard to use with a keyboard, a screen reader, or any other assistive technology, tell us through the Contact us form on our website. Include the page and what happened, and we'll look into it.

Last reviewed: 14 October 2026.