This policy is tailored to the current website build. The operating legal entity, address, governing law, service providers, and dedicated contact details must be confirmed in site-config.js before public data collection or paid enrollment begins.
1. Our commitment
Rainbow Sanctuary aims to align the website with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Accessibility is treated as continuing work rather than a one-time certificate.
2. Current status
This pre-launch build has been reviewed during development for keyboard use, focus visibility, text alternatives, semantic headings, labels, reduced motion, contrast, and responsive layout. It has not yet received a formal WCAG conformance audit, so we do not claim full conformance.
3. Measures already taken
- a skip link and visible keyboard focus styles;
- semantic landmarks, headings, labels, and descriptive link text;
- alternative text and provenance captions for meaningful imagery;
- reduced-motion behavior for animated and reveal effects;
- mobile-first layouts and controls sized for touch;
- clear form status and error announcements;
- plain-language scope and safety notices.
4. Known limitations
The site is still a prototype in a custom component format. Final testing is required after it is deployed on the production platform, after real images and third-party form, booking, payment, video, or map tools are connected, and with representative screen-reader and browser combinations. Some long legal and program pages may benefit from further plain-language or translated versions.
5. Accessibility feedback
If you cannot access content or complete a task, contact the accessibility contact listed before launch. Please describe the page, the barrier, your browser or assistive technology if you are comfortable sharing it, and the format or help you need. We aim to acknowledge accessibility feedback within five business days.
6. Assessment and review
The current statement is based on developer self-evaluation. A production accessibility review should include automated checks, keyboard-only testing, zoom and reflow, contrast, screen-reader testing, form submission, reduced motion, and testing on current mobile and desktop browsers. This statement should be reviewed after major changes and at least annually.