Accessibility

We design AHNOU to be usable with a keyboard, a screen reader, or a touchscreen, and we treat accessibility issues as bugs, not suggestions. A wedding invitation nobody can read is not an invitation

We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA - the level most accessibility law points to. We are partially conformant today: most of AHNOU meets it, and the parts that do not are listed below rather than quietly left out. We would rather tell you where we stand than claim a badge we have not earned

Readable text sizes and color contrast, labels on every form field, keyboard access to every action with a visible focus outline, and semantic headings so screen readers can navigate. Decorative visuals are marked as decorative so they stay out of the way. Pages stay usable when text is enlarged, and nothing on AHNOU flashes

Couples customize colors and fonts, so we keep every template’s defaults accessible and the RSVP flow readable in all of them. If a customization would make text hard to read, we aim to warn about it in the builder. A published site is the couple’s to edit, so their own words, photo captions, and image descriptions are theirs to get right - and we make room for that in the editor

When a guest leaves to pay at PayPal or to buy a gift at a retailer, they are on someone else’s site under that company’s accessibility standards, not ours. If you hit a barrier there, tell us anyway - it helps us decide who to link to

If anything on AHNOU is hard to use with your setup, email contact@ahnou.com - a real person reads it and answers. Tell us the page, what you were trying to do, and what you browse with if you know it. We aim to reply within five working days, and if a fix will take longer we will say so and find you another way to get it done in the meantime

If our answer does not solve it, say so and it goes to whoever can actually fix it rather than back into a queue. We would always rather hear it directly than have you give up on the page