Accessibility Statement

Accessibility for everyone

We build RiseVerse at https://riseverse.com to work for everyone. Keyboard navigation, screen reader support, proper color contrast are core features, not add ons. This page explains our accessibility approach and how to report any issues.

1. Our approach

Accessibility shapes how we build from the start. We follow WCAG 2.1 Level AA guidelines as our technical standard. Every component uses semantic HTML. We test keyboard navigation on every page. We verify focus states and color contrast in Chrome DevTools.

When you report an issue, we reproduce it, fix it, and test the fix. It's an ongoing process. We're always improving based on real user feedback.

2. What works well

We've put effort into getting the fundamentals right:

• Keyboard navigation - Tab through everything, use arrow keys in menus, escape to close modals. No keyboard traps that lock you in.
• Focus indicators - Clear visible focus rings on all interactive elements so you always know where you are.
• Color contrast - Text and interactive elements meet WCAG AA standards (4.5:1 for normal text, 3:1 for large text).
• Touch targets - 24px minimum on desktop. We aim for 44px on mobile (still implementing this).
• Semantic HTML - Proper heading hierarchy, form labels, and ARIA attributes where native HTML isn't enough.
• Status without color - Success, errors, and warnings use icons and text, never color alone.

3. Browser and assistive technology

RiseVerse works best with Chrome. Also works great with Edge, Firefox, and other Chromium-based browsers. Safari is not recommended for the best experience. The clipboard API has limitations that prevent reliable copying of components to Webflow.

The platform supports screen magnifiers, voice control software, and other assistive technologies. Using standard HTML and ARIA patterns means your tools should work with RiseVerse.

4. Known limitations

We're transparent about what still needs work. Third-party services like Stripe payment forms follow their own accessibility standards - we can't control those but we chose partners with strong accessibility practices.

Our component previews show visual examples but lack detailed alt text for screen readers - you might not know exactly what a component looks like before copying it. Keyboard shortcuts exist but aren't fully documented yet.

If you hit barriers we haven't listed, please tell us. We can't promise to fix everything, but we'll fix what we can and be honest about what we can't.

5. Feedback and support

Found something that doesn't work for you? Email accessibility@riseverse.com with:

• Page URL
• What went wrong
• Your assistive technology (if any)
• Browser and OS

We'll respond within 5 business days to acknowledge your report. Quick fixes like color contrast or focus states usually ship within 1 to 2 weeks. Complex changes that require restructuring take longer, but we'll keep you updated.

Your feedback directly improves RiseVerse. Every accessibility report helps us understand how real people use our platform with real assistive technology.

6. Standards we follow

We follow WCAG 2.1 Level AA standards, which align with Section 508, ADA, and EN 301 549 requirements. This is the legal standard in the US, EU, and many other regions. Level AA provides strong accessibility while maintaining clean design without the extreme constraints of AAA.

7. Questions? We're here to help