Barrierefreiheit

This document is written for a premium creator, subscription, digital content, and shop marketplace. It is intended to be read together with the other documents in the Legal Center.

1. Commitment

TrulyFeetFans aims to make core platform functions accessible, including navigation, account creation, login, subscription management, contact, legal information, and checkout-related flows.

2. Standard

The operational benchmark is practical alignment with WCAG 2.1 AA principles where feasible: perceivable content, operable controls, understandable flows, and robust compatibility with assistive technologies.

3. Known Areas for Improvement

• User-generated media may not always include complete captions or alternative text.
• Legacy components may require further keyboard and screen-reader refinement.
• Third-party checkout, verification, or embedded tools may have limits outside direct platform control.

4. Feedback

Accessibility barriers may be reported to info@trulyfeetfans.com with URL, device, browser, assistive technology, and a description of the barrier.

5. Remediation

Reports are reviewed based on severity, affected workflow, legal priority, and technical feasibility. Where immediate remediation is not possible, support may provide a reasonable alternative access path.

6. Legal Reference

Directive (EU) 2019/882 (European Accessibility Act).

7. Functional Accessibility Goals

• Navigation should be possible with keyboard controls for core public pages and account workflows.
• Interactive controls should have meaningful labels, visible focus states, and predictable behavior.
• Color should not be the only method for communicating important information.
• Legal pages and support pages should remain readable on mobile and desktop without horizontal scrolling.
• Forms should provide useful error messages and preserve entered data where feasible.

8. Third-Party Components

Payment, identity verification, chat, embedded media, analytics, or captcha providers may control their own accessibility behavior. Where a third-party component blocks access, users may contact support for an alternative path where feasible.

9. Procurement and Product Review

When adding new public-facing services, the platform should consider accessibility impact, keyboard usability, screen-reader semantics, color contrast, responsive behavior, and error recovery.

10. Feedback Handling

Accessibility feedback is reviewed based on severity, affected user journey, reproducibility, and remediation effort. Critical barriers in account, payment, legal, or support flows receive higher priority.

11. Documentation

The platform may keep internal notes on known barriers, remediation status, third-party dependencies, and accessibility-related support requests.

12. Public Legal Page Accessibility

Legal and policy pages should remain readable without login, should support browser zoom, should avoid text embedded only in images, and should present headings in a logical order for assistive technologies.

13. Payment and Subscription Access

Because payment and subscription management affect user rights, barriers in these flows are treated as important. Users who cannot complete a required action due to accessibility barriers may contact support for a reasonable alternative.

14. Content Creator Responsibilities

Creators are encouraged to use descriptive captions, avoid misleading thumbnails, and provide context for media where reasonable. User-generated content may not always be fully accessible, but platform controls should support better accessibility over time.

15. Review Cycle

Accessibility commitments should be reviewed periodically when major interface changes, checkout changes, verification changes, or new public pages are launched.

Last updated: 2026-06-14

Important note: These policies provide the platform operating framework and should be reviewed against the final legal entity details, tax registration, merchant acquiring requirements, and local consumer-law advice before launch in each target jurisdiction.