Accessibility Statement
Last updated: August 25, 2026
1. Current status
We completed automated testing and code review of representative public pages on August 25, 2026 and fixed the verified color contrast failures in the shared interface and the audited homepage and pricing-page demonstrations. Those tested pages passed the supported automated WCAG A and AA rules after the fixes. We have not completed enough manual and authenticated-product testing to make a service-wide WCAG 2.2 conformance claim, so this work is ongoing.
2. What we do
- Use semantic page structure, descriptive labels, and keyboard-operable controls.
- Provide visible keyboard focus and respect reduced-motion preferences.
- Check shared colors and interface components against WCAG contrast requirements.
- Include accessibility checks in design, development, and quality review.
- Review feedback from people with disabilities and prioritize barriers that block access.
3. Known limitations
Creator-hosted sites can contain colors, images, videos, documents, and text supplied by the creator. Cabana provides accessible defaults and contrast safeguards where the site builder controls the presentation, but we cannot guarantee that every creator-supplied item includes captions, text alternatives, accessible document structure, or clear link wording. Some connected third-party services and embedded content are also outside our direct control.
If you find a barrier in Cabana’s own interface or in a site we host, please tell us. We will investigate whether the issue is in the platform, the creator’s content, or a third-party service and explain what we can do next.
4. Feedback and support
Email privacy@cabanastudio.io with “Accessibility feedback” in the subject. Please include the page address, what you were trying to do, and the browser or assistive technology you used if you are comfortable sharing it. We aim to acknowledge accessibility reports within five business days and will provide the same information or service in another reasonable format when we can.
5. Assessment approach
We assess accessibility through code review, keyboard and responsive checks, automated WCAG scans, and testing at the rendered page boundary. The August 25, 2026 assessment sampled the homepage, pricing page, a legal page, and both rendering paths for creator-built site footers.