← Legal

Legal document · OWNER APPROVED

Accessibility Statement

Owner-approved 0.2.0 text. This page is not published, legally effective, or authorized for production deployment.

OWNER APPROVED — 0.2.0

NOT PUBLISHED — DEPLOYMENT AUTHORIZATION NOT GRANTED

Accessibility Statement

Slug: /legal/accessibility Version: 0.2.0 Status: OWNER APPROVED — 0.2.0 Proposed effective date: [PROPOSED EFFECTIVE DATE] Audience: Players, visitors, Store customers, supporters, guardians, and anyone who needs accessibility information or wants to report an accessibility barrier.

Plain-language summary

Eidolon Gaming intends Echoes of Eidolon and its related web experiences to be usable by people with disabilities. This statement describes the accessibility practices the product is working to support, areas that require continuing validation, and how to report barriers. It does not claim full WCAG conformance or independent certification.

Table of contents

  1. Our accessibility commitment
  1. Conformance language
  1. Keyboard access and focus
  1. Motion and animation
  1. Contrast, text, and visual presentation
  1. Audio, captions, and transcripts
  1. Puzzles and equivalent presentation
  1. AI-mediated interaction accessibility
  1. Known limitations
  1. Third-party services
  1. Accessibility feedback
  1. Ongoing improvement
  1. Contact and help routes
  1. Related documents
  1. What changed / version notes

1. Our accessibility commitment

Eidolon Gaming is committed to improving access to Echoes of Eidolon, account services, legal pages, support flows, and Store experiences. Accessibility is an ongoing engineering and content responsibility rather than a one-time certification. We aim to identify barriers, prioritize issues that prevent meaningful access, and improve features as the product evolves.

2. Conformance language

This version does not claim that Echoes of Eidolon or every related web page fully conforms to WCAG at any particular level, and it does not represent that an independent audit has certified full conformance. We use recognized accessibility practices and relevant WCAG success criteria as references when designing, testing, and remediating features. Any future conformance claim should be made only after the applicable scope and evidence have been verified.

3. Keyboard access and focus

Interactive web controls should be operable without requiring a mouse where keyboard operation is reasonably applicable. Focus order should follow the intended reading and interaction sequence, visible focus states should make the current control understandable, and keyboard users should be able to reach and leave interactive components without becoming trapped.

Complex game interactions can require feature-specific alternatives. If a control cannot yet be completed with a keyboard-equivalent path, that is an accessibility limitation to report rather than something this statement silently treats as solved.

4. Motion and animation

Where the interface uses significant motion, camera movement, animated transitions, flashes, or other potentially disruptive effects, we aim to respect reduced-motion preferences where technically appropriate and provide alternatives for essential information that would otherwise be communicated only through motion. Accessibility accommodations should not require a user to give up necessary gameplay information.

5. Contrast, text, and visual presentation

We aim for readable contrast, text that can be enlarged without unnecessarily losing information or controls, labels that do not rely solely on color, and layouts that remain understandable at increased zoom or text size where the platform permits. Decorative visual fidelity should not be treated as more important than access to essential instructions, status, or transaction information.

6. Audio, captions, and transcripts

Where meaningful prerecorded speech, dialogue, or other audio conveys information needed to understand content, captions, transcripts, or an equivalent text presentation should be provided where applicable and technically feasible. If live or generated audio is introduced, its accessibility support must be evaluated separately rather than assumed to be covered by prerecorded-content practices.

7. Puzzles and equivalent presentation

Echoes of Eidolon can include difficult puzzles. Accessibility does not require making every puzzle easy or eliminating the underlying challenge. It does require considering whether a puzzle is unintentionally impossible because essential information is available only through one sensory or motor mode.

Where practical, puzzle information should have an equivalent presentation that preserves the intended reasoning challenge—for example, text equivalents for necessary audio cues, non-color-only indicators, or keyboard-accessible interaction paths. An equivalent presentation may differ in form while preserving the substantive puzzle objective.

8. AI-mediated interaction accessibility

AI-mediated characters and systems can produce dynamic text or voice output. Text interaction is not limited by the current Member voice-window perk. We aim to keep essential conversation information available in a form compatible with the interaction mode being used. Dynamic content should not be assumed accessible merely because it is generated as text; focus management, announcements, timing, and interface behavior can also create barriers.

9. Known limitations

Because the product is evolving, known or discovered limitations may include complex visual game scenes, experimental interfaces, motion-heavy sequences, dynamic AI output, puzzle mechanics, and third-party checkout or fulfillment pages that are not fully controlled by Eidolon Gaming. Current verified known limitations for deployment should be maintained here: [VERIFIED ACCESSIBILITY LIMITATIONS].

This placeholder must be replaced with the live product's actual limitations before publication if material barriers are known. We do not use the absence of a listed limitation as proof that no barrier exists.

10. Third-party services

Some flows rely on third-party services, including Stripe for payment processing and Printful for merchandise fulfillment. Eidolon Gaming should choose and configure integrations with accessibility in mind, but some hosted interfaces may be controlled by the provider. If a third-party barrier prevents a transaction or required action, report it so we can investigate an alternative path or work with the provider where feasible.

11. Accessibility feedback

Use /contact and select Accessibility feedback to report a barrier. Helpful information can include the page or feature, what you were trying to do, the assistive technology or input method involved if you choose to share it, and what happened. Do not include passwords, payment-card data, access tokens, recovery codes, government IDs, or other unnecessary sensitive information.

We may acknowledge a report and ask focused follow-up questions. We do not promise a fixed resolution time because severity, technical complexity, provider dependencies, and testing requirements vary. Reports that prevent account access, safety, payment, or core participation should be triaged accordingly.

12. Ongoing improvement

Accessibility improvements may be delivered through design changes, code fixes, content corrections, alternative presentations, provider configuration, or documentation. Product updates can also introduce new barriers, so regression testing and user feedback remain important. Material accessibility changes do not remove mandatory rights under applicable law.

13. Contact and help routes

Accessibility feedback: /contact → Accessibility feedback. Player support messages should be sent from the Support tab, not this webform.

Player/account/gameplay support: /account/support. Signed-out users seeking Player Support should sign in and return there.

Store/order support: [STORE/ORDER SUPPORT ROUTE].

14. Related documents

See the Terms of Service, Privacy Policy, Cookie Policy, Acceptable Use and Player Conduct policy, and AI/Automated Interaction Disclosure. Accessibility requests involving a specific transaction may also be governed by the relevant Store, Membership, Donations, or Refund policy.

15. What changed / version notes

Version 0.2.0 establishes the owner-approved accessibility statement without asserting unverified WCAG conformance. It covers keyboard access, focus, reduced motion, contrast, text scale, captions/transcripts, equivalent puzzle presentation, dynamic AI interaction, known-limitations disclosure, and the dedicated accessibility-feedback route.