Festival planning should be open to everyone. We want people with disabilities to be able to read our guides, explore events, and use our planning tools.
1. Our commitment
We aim to make RaveHacks usable with a keyboard, assistive technology, mobile devices, and browser accessibility settings. Accessibility is an ongoing part of maintaining the site, not a one-time badge.
2. Our target and current status
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These guidelines address a range of visual, hearing, motor, speech, cognitive, and other access needs.
This statement is a commitment and a description of our approach—not a certification that every page or feature conforms. A completed, site-wide conformance assessment is not available for this statement, so we are not claiming full WCAG or legal compliance.
3. What we are working toward
Our priorities include clear headings and labels, meaningful link text, readable contrast and text sizing, visible keyboard focus, alternatives for meaningful images and media, and layouts that remain usable when zoomed or viewed on a smaller screen.
The shared site layout includes a “Skip to content” link. These legal pages use a consistent structure, section links, and direct navigation between policies. Those features help with navigation but do not, by themselves, establish conformance.
4. Alternatives for finding information
If the interactive map is difficult to use, try the Festival Finder list or Festival Calendar. These offer other ways to browse event information.
If a guide, image, form, or tool creates a barrier, contact us for assistance or to request the information in a more usable format. Tell us what you are trying to do; you do not need to disclose a disability or medical information.
5. Areas that may need improvement
Interactive maps, third-party signup forms, embedded media, external ticketing sites, and older or newly added editorial content may present barriers. These are areas to review, not a claim that every instance has been tested or a complete list of verified failures.
Some external services are outside our direct control. We still welcome reports and will consider an alternative way to provide the relevant RaveHacks information. An external provider’s statement does not establish the accessibility of our own site.
6. Report a problem or request help
Email [email protected] with the subject “Accessibility.” Helpful details include the page address, what you were trying to do, what went wrong, and your preferred way to receive a reply. Your browser, device, or assistive technology can help us reproduce the issue, but providing those details is optional.
We will review the report, explain what assistance or next steps are available, and work toward resolving barriers within our control. Please do not include passwords or other sensitive information.
This is not an emergency contact channel. For an urgent incident at an event, contact on-site staff or emergency services.
7. Keeping this statement current
We will update this statement as accessibility work, testing, and known limitations become better documented. The date on this page indicates the latest revision. Feedback helps us prioritize improvements that affect real visitors.