Accessibility Compliance (WCAG 2.1)

Vexor is committed to delivering an inclusive and accessible platform for all users. This policy explains our compliance with WCAG 2.1 accessibility standards, the technical and organizational measures we apply, and how users may report accessibility concerns.

1. Commitment to Accessibility

Vexor aims to provide an inclusive experience for users of all abilities. Accessibility is embedded directly into our product design, engineering, content creation, and testing processes. We follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA where required and practical, ensuring that every user can interact with our platform without unnecessary barriers.

2. Standards & Scope

Our accessibility program is aligned with industry standards and legal requirements, including:

  • WCAG 2.1 (Levels A and AA)
  • WAI-ARIA Authoring Practices
  • Platform-specific accessibility guidelines for iOS and Android
  • Local accessibility and anti-discrimination laws

This policy covers web interfaces, PWAs, mobile apps, in-app features, creator tools, media content, and third-party integrations where technically feasible.

3. Key Accessibility Features

  • Keyboard Navigation: All interactive elements are fully keyboard-operable.
  • Focus Management: Visible focus outlines and logical navigation order.
  • Screen Reader Support: Semantic HTML, ARIA roles, labels, and live regions.
  • Color Contrast: All text meets WCAG 2.1 contrast ratios.
  • Resizable Text: UI adapts to font-size changes up to 200% without layout issues.
  • Alt Text & Media Transcripts: Meaningful descriptions for images and transcripts for audio/video.
  • Accessible Forms: Labels, validation messages, and error explanation references.
  • Consistent Navigation: Predictable layouts using headings and landmarks.
  • Captions & Subtitles: Available for uploaded videos; auto-captioning where possible.
  • Reduced Motion Support: Respect system preferences to reduce animations.

4. Design & Development Practices

Vexor integrates accessibility throughout the product lifecycle:

  • Design teams use accessible components and validated color palettes.
  • Developers apply semantic markup and ARIA patterns consistently.
  • Content creators receive accessibility guidelines and tools.
  • Pull requests include required accessibility checks.
  • Automated linters enforce common accessibility rules.

5. Automated & Manual Testing

  • Automated Tools: Axe, Lighthouse, CI accessibility linters.
  • Manual Audits: Keyboard-only testing, screen reader flows (NVDA, VoiceOver).
  • User Testing: Sessions with users with disabilities.
  • Regression Testing: Accessibility checks integrated into release pipelines.

6. Media Accessibility

For videos, livestreams, and audio content:

  • Closed captions or subtitles provided for on-demand video.
  • Transcripts for major audio content and podcasts.
  • Auto-captioning is generated when available.
  • Creators can edit auto-captions for accuracy.
  • Live captions for high-traffic events when feasible.

7. Third-Party Content & Integrations

All third-party vendors must meet Vexor’s accessibility expectations. External content that is not fully accessible is flagged for remediation, alternatives, or explanatory guidance to affected users.

8. Accessibility for Creators

Creators are offered tools to improve accessibility in their content:

  • Captioning tools and best-practice guides
  • High-contrast templates
  • Guidance on writing descriptive alt text
  • Recommendations on accessible design (color, layout, font size)

9. Reporting Accessibility Issues

Users may report accessibility issues using the contact information below. We prioritize reports affecting safety, user onboarding, account recovery, and monetization flows.

Email: accessibility@vexor.to
Support: support@vexor.to

10. Accessibility Roadmap & Targets

  • Achieve WCAG 2.1 AA across all core flows.
  • Expand auto-captioning and multilingual subtitle support.
  • Increase languages available for UI translations.
  • Continue user testing with diverse accessibility communities.

11. Limitations & Exemptions

Due to the nature of user-generated content (UGC), some elements may not fully meet WCAG standards. Vexor provides tools and education to help creators improve accessibility wherever possible.

12. Legal Compliance & Accessibility Officer

For legal inquiries or formal compliance matters:
Email: accessibility@vexor.to
Compliance: compliance@vexor.to

13. Training & Internal Awareness

  • Mandatory WCAG & ARIA training for product and design teams.
  • Assistive technology testing training (NVDA, VoiceOver).
  • Inclusive writing and content creation workshops.

14. Accessibility Statements & Conformance

Vexor may publish feature-level accessibility statements outlining conformance, known issues, and remediation timelines for transparency and compliance.

15. Changes to This Policy

This policy is updated as new standards emerge, user feedback is incorporated, or accessibility improvements are released. Updated versions will include a revision date.

War diese Antwort hilfreich? 0 Benutzer fanden dies hilfreich (0 Stimmen)