Accessibility at Tangled

Last reviewed: 18 Oct 2025

Scope (India & Global)

This statement covers our India experience and provides a global baseline. For India, we reference Indian laws, guidance, and regulators. For all regions, our primary reference is the W3C Web Content Accessibility Guidelines (WCAG). Country-specific details will be added as we publish region-specific statements.

This statement covers our public website and in-app web views. Native mobile app features follow the same accessibility goals, with phased rollout.

Our commitment

We want everyone to connect and feel included on Tangled. We design and build with accessibility in mind so that as many people as possible can use our products—regardless of device, context, or ability.

Standards we reference

  • W3C WCAG 2.2 — our primary global reference for accessibility on the web.
    Our aim is WCAG 2.2 Level AA for web content and components (non-binding).
  • GIGW 3.0 (Guidelines for Indian Government Websites/Apps, MeitY) — we take guidance from GIGW 3.0, which maps to WCAG.
    Maps to WCAG and offers India-specific guidance.
  • Rights of Persons with Disabilities (RPwD) Act, 2016 and associated Rules — we reference the Act’s principles of non-discrimination and accessibility for information and communication technology (ICT) where applicable.
  • EN 301 549 (EU accessibility requirements for ICT) — referenced where applicable for global markets.
  • Inclusive design practices for Indian users, devices, languages, and networks (e.g., support for system text scaling, reduced motion, and low-bandwidth scenarios).

Conformance status

We use WCAG 2.2 Level AA as our benchmark. We are partially conformant: most content and components are designed to meet Level AA; some items are still being improved. See Known limitations for details, and contact us if you encounter a barrier.

What’s built to work for you

  • Keyboard access: Interactive elements are designed to be reachable and operable via keyboard; visible focus indicators help you track where you are.
  • Screen readers: Landmarks, headings, labels, and live regions are provided for meaningful navigation and announcements.
  • Contrast & colour: Text and essential UI are designed to meet a 4.5:1 contrast ratio (3:1 for large text and UI). Colour is never the only way we convey meaning.
  • Text scaling: Layouts support zoom and OS text-size settings up to 200% without loss of functionality in typical flows.
  • Motion & animation: We respect “Reduce motion” settings and avoid effects that could trigger discomfort.
  • Media alternatives: Captions, transcripts, and alt text are provided where applicable and practical.

Note: Some aspects of accessibility can be subjective and may vary by individual perception, assistive-technology configuration, device, or browser. We continuously test and refine to improve consistency across experiences.

Compatibility

We test Tangled on current iOS/Android and modern desktop browsers (Chromium-based, Firefox, Safari), with assistive technologies commonly used in India such as VoiceOver, TalkBack, and NVDA.

Availability & rollout

  • Phased rollout: Some improvements may be in phased release and not visible to every account at the same time.
  • Availability may vary: Practical availability can depend on your device/OS version, browser, assistive technology setup, network, and settings.
  • Planned availability: Items labelled “Coming soon” are roadmap targets and may change in scope or timing.

If something listed here isn’t yet available to you, please contact us via the Contact Us page so we can help or suggest alternatives.

Known limitations

We are actively improving the following areas:

  • More descriptive labels for a few legacy buttons in older pages.
  • Additional captions for some historical video assets.
  • Refinements to keyboard order within complex modals.

If you encounter an issue that isn’t listed here, please contact us.

Feedback & requests

Your feedback helps us prioritise fixes. If you need content in an alternative format, encounter a barrier, or have a suggestion, contact us:

When possible, include the page or screen name, what you were trying to do, your browser or device, and any assistive tech you use.

We acknowledge within 2 business days and aim to resolve or offer a workaround within 15 business days.

How we improve

  • Design tokens and components are audited for colour contrast and focus states before rollout.
  • Automated checks run in CI alongside manual screen reader and keyboard testing.
  • We review changes using WCAG 2.2 criteria as a reference and document outcomes.

Third-party content

Some pages may include third-party widgets or content outside of our full control. We work with partners to encourage accessible implementations and provide alternatives when feasible.