Accessibility Statement

Accessibility Statement

TradingView is committed to providing an inclusive experience. This statement explains our accessibility goals, the scope of coverage, how we evaluate accessibility, known limitations, and how to request assistance or report issues.

Conformance target
WCAG 2.1 Level AA (target)
Scope
Primary web pages & core user journeys
Last updated
2026-02-12
On this page: Commitment Standard Scope Supported features Testing Known limitations Feedback FAQ

1) Commitment

We design and maintain our website to support access for as many people as possible, including users who rely on assistive technologies. Accessibility is treated as an ongoing quality practice: we build with standards in mind, test regularly, and prioritize fixes based on impact.

2) Standard and conformance target

Our target is to align with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for key pages and primary workflows. Because our product and content evolve, full conformance may vary by page or feature at any given time.

Important note This page describes our target and continuous improvement process. If you encounter a barrier, contact us and we will provide help or an alternative way to access the information.

3) Scope of this statement

This statement applies to our public website at travdisgview.com, including the English pages under /en/. It focuses on accessibility of page structure, navigation, readable content, and core interactions.

  • Included: navigation, informational pages, forms, and core UI components on the public site.
  • May vary: third-party embedded content, external links, and user-generated or community content.

4) Accessibility features we support

We work to support the following capabilities across major browsers and devices.

Keyboard navigation

Access key controls without a mouse, with predictable focus order and visible focus indicators for primary UI elements.

Screen reader compatibility

Semantic structure and ARIA where needed to improve navigation and understanding with common screen readers.

Color contrast & themes

Design choices aimed at readable contrast, plus theme options and chart palette customization where available.

5) How we evaluate accessibility

We use a combination of automated checks and manual reviews. Testing typically includes keyboard-only navigation, screen reader spot checks, and contrast verification for key templates.

  • Automated: linting and accessibility scanners on representative pages.
  • Manual: keyboard traversal, focus order, landmarks, headings, and form usability.
  • Assistive tech: spot checks with popular screen readers (environment-dependent).

6) Known limitations

Despite ongoing work, some content may not fully meet our target in all contexts. Examples may include:

  • Complex interactive visualizations may have reduced screen reader support compared to text equivalents.
  • Third-party embedded media may not always provide complete captions or transcripts.
  • Older pages or legacy templates may not yet match the latest accessibility patterns.

7) Feedback and contact

If you experience an accessibility barrier, please contact us. Include the page URL, what you were trying to do, your device/browser, and any assistive technology used.

Accessibility support email
[email protected]
Response timeframe
We aim to respond within a reasonable time

If you require information in an alternative format, we will work with you to provide an accessible equivalent where feasible.

FAQ

We target alignment with WCAG 2.1 Level AA for key pages and primary workflows, and we continuously improve as the site evolves.

Email [email protected] with the page URL, a short description of the problem, your device/browser, and any assistive technology used.

Yes. If you cannot access information or complete an action, contact us and we will provide reasonable assistance or an alternative method where feasible.