Last updated: September 2026
HackSpace is committed to making its platform accessible to everyone, including people with disabilities. We strive to comply with the WCAG 2.2 AA international standard across the entire platform — the marketing site, hackathon pages, registration forms, and the admin panel.
This statement explains our accessibility efforts, the features we support, known limitations, and how you can report accessibility issues.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at conformance level AA, as published by the World Wide Web Consortium (W3C).
WCAG 2.2 AA covers a wide range of recommendations for making web content more accessible to people with sensory, motor, and cognitive disabilities.
We continuously audit and improve the platform to address accessibility gaps identified through testing and user feedback.
Keyboard navigation: All interactive elements — menus, buttons, forms, dialogs, and tabs — are reachable and operable using the Tab, Enter, Space, and Escape keys. A "Skip to main content" link is provided on every page.
Screen reader support: We use semantic HTML landmarks (header, nav, main, footer), proper heading hierarchy (h1 through h3), ARIA labels for icon-only buttons, and live regions for dynamic content updates.
Visual accessibility: We maintain color contrast ratios of at least 4.5:1 for normal text and 3:1 for large text and UI components. Color is never used as the sole indicator of state — icons and text labels always accompany it.
Reduced motion: We respect the `prefers-reduced-motion` system preference. When enabled, animations and transitions are minimized.
Text scaling: The platform supports text scaling up to 200% without loss of content or functionality.
Forms: All form inputs have associated labels, error messages are programmatically announced, and required fields are clearly indicated.
While we strive for full compliance, some areas of the platform may still have accessibility gaps:
Some third-party embedded content (such as YouTube videos, Google Maps embeds, and external links) may not fully meet WCAG 2.2 AA. We recommend checking the accessibility statements of those services directly.
The badge designer canvas and some drag-and-drop interactions in the admin panel may be difficult to operate with keyboard alone. We are working on alternative keyboard-accessible controls for these features.
Some older content pages may not have perfect heading hierarchy. We are continuously auditing and fixing these issues.
If you encounter a specific accessibility barrier, please report it so we can prioritize a fix.
We welcome feedback on the accessibility of HackSpace. If you encounter an accessibility barrier or have a suggestion for improvement, please let us know.
When reporting an issue, please include:
• A description of the problem you encountered
• The page URL where the issue occurred
• The type of assistive technology you were using (if any)
• Your contact information so we can follow up
You can report issues through our Contact page or by sending an email to the platform administrators. We aim to respond to accessibility reports within 2 business days and to implement fixes as soon as possible.
Accessibility is an ongoing process. We are committed to:
• Conducting regular accessibility audits of new and existing features
• Training our development team on WCAG 2.2 AA requirements
• Incorporating accessibility checks into our development workflow
• Responding promptly to user-reported accessibility issues
• Improving keyboard, screen reader, and cognitive accessibility over time
For any questions about this accessibility statement or to report an accessibility issue, please contact us through the Contact page.
We are committed to making HackSpace accessible to everyone and value your input.