Accessibility Statement

This statement covers the LootBox web app served at lootbox.example, including the user-facing site and the player account area. It does not cover the admin panel (an internal staff tool) or third-party services we link to.

We target Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Where a specific success criterion is not yet met, it is listed in §5 "Known limitations" along with our remediation plan.

This page is a draft. The final conformance claim will be backed by a third-party audit completed before production launch.

• Keyboard navigation across every interactive element with a logical tab order
• Visible focus styles on every focusable control (Electric Green outline)
• Semantic landmarks (header, nav, main, footer) and ARIA labels on icon-only buttons
• Screen-reader-compatible markup tested against NVDA + VoiceOver
• Reduced-motion preference (prefers-reduced-motion) respected for the case opening reel, battle animations, and homepage live-feed ticker
• Skip-to-content link on long static pages
• Form inputs paired with explicit labels, helper text, and error messages
• Minimum tap target size of 44 × 44 px on mobile
• Minimum 4.5:1 text contrast against background; 3:1 for large text
• Minimum supported viewport: 360 px wide (mobile portrait)
• Live-region announcements for case opening result and battle-round transitions

We test against the following combinations and aim to support any equivalent setup:

• Browsers: latest two stable releases of Chrome, Firefox, Safari, and Edge
• Screen readers: NVDA on Windows, VoiceOver on macOS / iOS, TalkBack on Android
• Operating systems: Windows 10+, macOS 12+, iOS 16+, Android 12+
• Zoom: up to 200% on desktop, 400% with reflow on mobile
• Browser dev-tool feature emulation (forced colours, prefers-reduced-motion, prefers-contrast)

• The animated case-opening reel uses motion that, while reduced-motion-aware, may still feel intense for some users — let us know if you hit this.
• Complex tables (transaction history, withdrawal history) reflow on small screens but remain dense to read; we are improving the mobile layout.
• Some chart panels in admin Analytics use colour as the primary differentiator; these are admin-only and not in user-facing scope.
• Live region timing during fast battle rounds may produce overlapping announcements for screen-reader users.

• Automated linting in CI: axe-core runs against every shared component story in the design system
• Manual review at each release: one engineer keyboard-walks the critical flows (signup, deposit, withdraw, open case, battle)
• User feedback channel (see §7) feeds directly into the next sprint
• Annual third-party audit prior to each major version

If you encounter a barrier, please write to accessibility@lootbox.example or use the Support form. Provide the page URL, your assistive technology, and a short description of the problem. We respond within 5 business days and prioritise issues that block core flows (signup, deposit, withdrawal).

If you are dissatisfied with our response and reside in the European Union, you can escalate under the EU Web Accessibility Directive (2016/2102) by contacting the national supervisory authority in your member state. We will cooperate fully with any accessibility-related investigation.

For users outside the EU, please contact accessibility@lootbox.example with the subject line "Formal complaint" and we will route it through our internal escalation path.