Accessibility
Effective
Planning a wedding is stressful enough. Nobody should have to fight the website too. This page says what we build to, what we have actually done, what we know is not there yet, and how to tell us when we have got it wrong.
The standard we build to
We target the Web Content Accessibility Guidelines 2.2, Level AA. That is the bar we hold new work to and the bar we measure complaints against.
We have not commissioned an independent audit, so this is a statement of the standard we work to and what we have done — not a claim of certified conformance. When that changes, this page will say so.
What we have done
- Real HTML structure. Headings are headings, lists are lists, and the legal pages are one linear reading order with no decorative markup in the way.
- Keyboard operation. Everything interactive is reachable and operable from the keyboard, with a visible focus ring on every focusable element rather than the browser default being suppressed.
- Motion is optional. The entrance animations on the home page are switched off for anyone whose system asks for reduced motion.
- Colour is never the only signal. Anything the palette distinguishes is also distinguished by text or shape.
- Text that scales. Type is sized in relative units, so browser zoom and larger default text sizes reflow the page instead of clipping it.
- No JavaScript required to read the legal pages.The words on these pages are rendered on the server, so they are readable with scripting disabled or blocked. The pages do still load the framework’s own scripts, and the analytics pixel when one is configured — see the Privacy Policy for what that collects.
What we know is not there yet
Listing these is more useful to you than a badge would be.
- No independent audit. Our testing is our own — keyboard, zoom, and screen-reader passes by the people who built the pages. That catches a lot, and it is not the same as an expert review.
- The Recovery Plan PDF. Your plan is delivered as a generated PDF, and we cannot yet confirm that it is fully tagged for screen readers. If the PDF is a barrier for you, ask us and we will get you the same content in a format you can use.
- Checkout.Payment is handled on our payment processor’s own hosted page, which we do not control. If you hit a barrier there, tell us — we will help you complete the purchase another way and raise it with them.
- Documents you upload. A scan or a photo of a contract is only as readable as the file itself. That is a limit of the source material, not something we can fix downstream, but it is worth knowing before you send one.
Reporting a barrier
Write to help@weddingremedy.com and describe what happened. We treat an accessibility barrier as a defect, not a feature request, and every report gets a reply from a person.
If you can, include:
- The page you were on, and what you were trying to do.
- Your browser, and any assistive technology you were using — a screen reader, magnification, voice control, switch access.
- What happened instead of what you expected.
None of that is required. “The quiz will not let me past step three with a keyboard” is a perfectly good report.
If something here blocks you
Do not fight it. Tell us what you were trying to do — send us your documents, read what we found, buy the plan — and we will get you the same outcome another way, at the same price. Uploading and being analysed cost nothing, so an inaccessible step there does not just cost you a purchase, it costs you the answer. An inaccessible step is our problem to solve, not yours to work around.
See also our Privacy Policy, our Terms of Service, and how every figure is counted.