Legal

Accessibility Statement

Last updated: April 16, 2026

HitScanTCG is committed to making our website and desktop application usable by people with the widest possible range of abilities. We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, and we welcome feedback on where we fall short.

1. Our Commitment

We believe everyone should be able to discover trading card products, follow livestreams, and manage their subscription regardless of disability or assistive technology. We design new features with accessibility in mind, test against WCAG 2.1 Level AA criteria, and treat accessibility defects as product bugs rather than optional improvements.

2. Conformance Target

Our target is WCAG 2.1 Level AA. This means, among other things:

  • Meaningful color contrast for all text (at least 4.5:1 for normal text, 3:1 for large text and UI components).
  • All functionality operable by keyboard alone.
  • Visible focus indicators for all interactive elements.
  • Skip-to-main-content links on every page.
  • Semantic HTML with appropriate ARIA attributes where needed.
  • Alternative text for informative images; decorative images marked as such.
  • Form fields with visible labels and descriptive error messages.
  • Live regions announcing dynamic content updates (queue progress, order status).
  • Tables with proper headers, captions where helpful, and scope attributes.
  • Content readable without a specific orientation (both portrait and landscape).
  • Support for browser zoom up to 200% without loss of functionality.
  • Support for user-provided CSS and reduced-motion preferences.

3. Known Limitations

We are actively working on the following known accessibility gaps. These are tracked as engineering issues and addressed in our launch and post-launch phases.

  • Live stream video player: Third-party stream embeds (Twitch, YouTube) inherit the accessibility features of those platforms. We do not override their controls.
  • Overlay graphics (Scanner Tool): The OBS overlay produced by the Scanner Tool is rendered graphically by design (for broadcast). Screen-reader-accessible alternates are not available for overlay content; the overlay is intended for viewers of the stream, not direct interaction by the Streamer.
  • Mobile dashboard: Full responsive layout is landing in a pre-launch phase. Until then, mobile users may encounter horizontal scrolling on dashboard pages.
  • Complex tables: Some admin tables on internal pages currently lack full ARIA; this is being corrected ahead of launch.
  • PDF documents: Any PDFs we publish (e.g., provisional patent) may not be fully tagged for screen readers. If you need accessible alternative access to a PDF, contact us.

4. Accessibility Features You Can Use

  • Keyboard navigation: Tab through every interactive element; Shift+Tab for reverse. Enter or Space to activate. Esc to close modals.
  • Skip link: Press Tab on page load to reveal a "Skip to main content" link.
  • Browser zoom: Ctrl/Cmd + = and Ctrl/Cmd + - to zoom. Supported up to 200%.
  • Reduced motion: We respect the prefers-reduced-motion media query. Enable reduced motion in your OS settings to minimize animations.
  • Dark interface: HitScanTCG uses a dark color scheme by default. We do not currently offer a light mode. Dark mode has been tested for WCAG AA contrast on all primary text and interactive elements.
  • Screen reader compatibility: Tested with NVDA (Windows) and VoiceOver (macOS). We prioritize fixes for any regression you report.

5. Compatibility

HitScanTCG’s website is designed and tested for the current and previous major versions of the following browsers:

  • Chrome (desktop, Android)
  • Safari (macOS, iOS)
  • Firefox (desktop)
  • Edge (Windows)

Older browsers and Internet Explorer are not supported. Some features may not work without JavaScript; we strive to make critical paths (login, checkout) functional with JavaScript enabled, which is standard for modern web applications.

6. Assessment and Testing

We perform automated accessibility testing (Lighthouse, axe-core) on every deploy and manual testing with keyboard-only navigation and screen readers before major releases. We also plan to engage an external accessibility audit after launch to validate our self-assessment.

7. Feedback and Accommodation Requests

If you encounter an accessibility barrier using HitScanTCG, or need an alternative way to use a feature, please contact us:

  • Email: accessibility@hitscantcg.com
  • Subject line: Please start with "Accessibility:" for triage.
  • Information to include: the URL or screen where you encountered the barrier, the assistive technology you were using (screen reader, voice control, switch access, etc.), your browser and operating system, and a description of what you were trying to do.
  • Response time: We aim to acknowledge within 3 business days and to provide a resolution or status update within 14 days.

8. Formal Complaints

If we are unable to resolve an accessibility issue to your satisfaction, you may file a complaint with:

9. Updates

We update this statement as our accessibility work progresses. Material improvements and any new known limitations will be reflected here with an updated date. We welcome requests for progress updates by email at accessibility@hitscantcg.com.