Accessibility

Accessibility Statement

Draft — pending legal review
⚠ Working draft. Publishing this commits you to it in practice, not just on paper — worth an actual accessibility audit (keyboard navigation, screen reader testing, color contrast) against WCAG 2.1 AA before this goes live, not just after a complaint.

Our commitment

We want Prizania to work for every owner, guest, and pro — including people using screen readers, keyboard navigation, or other assistive technology. This is an ongoing effort, not a box we checked once.

What we aim for

We design toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, where reasonably applicable — things like keyboard-friendly navigation, readable color contrast, descriptive alt text on meaningful images, clear form labels, and consistent page structure.

Where this can fall short

Some features rely on third-party integrations (payment processing, identity verification) we don't fully control the accessibility of. We encourage our partners toward the same standard but can't guarantee it.

Tell us if something's not working

If you hit a barrier using Prizania, let us know — what page, what you were trying to do, and what device or assistive technology you were using, if relevant. That's the fastest way for us to actually fix it rather than guess.

Contact

Prizania · accessibility@prizania.com