Legal

Accessibility statement

TrustFirst is committed to making investing literacy education available to as wide an audience as possible, including people with disabilities. This page describes our conformance level, known limitations, and how to report accessibility issues.

Last reviewed: 2026-05-20 · Effective: 2026-05-20

Conformance target

TrustFirst targets WCAG 2.1 Level AA conformance across every public and authenticated surface. We design with semantic HTML, sufficient color contrast, keyboard navigation, focus indicators, accessible form labels, and meaningful link text. New screens are reviewed against the WCAG 2.1 AA success criteria before they ship.

We have not yet undergone an independent third-party accessibility audit. We are committed to commissioning one before any B2B procurement engagement that requires audited conformance documentation.

Scope

This statement covers the entire trustfirst.turntwo.dev domain: public marketing pages (/, /for-families, /for-educators, /for-cpas, /pricing, /help, /glossary, /translate, /compare, /trust-ratings, /podcast, /newsletter), authenticated app surfaces (/dashboard, /learn, /markets, /portfolio, /cpa-dashboard, /cohorts, and sub-routes), and the admin console.

Known limitations

We disclose limitations transparently. Each item below is tracked internally with a remediation timeline.

  • Streaming AI responses: the AI tutor and translator stream tokens as they generate. Screen readers may not announce mid-stream updates predictably. Final response text is always announced when streaming completes.
  • Interactive chart controls: the Research Desk and What-If charts use Recharts. Hover-tooltip data is available via keyboard focus on data points, but the click-to-zoom interaction is mouse-only in some configurations.
  • Onboarding tour: the driver.js onboarding tour is dismissable with ESC and skippable. The tour overlay traps focus while active.
  • Lesson content from older batches: a small number of older lesson images may lack descriptive alt text. We are auditing and patching these in a rolling content-review pass.
  • PDF and audio outputs:CPE certificates render as browser-printable HTML (with semantic structure) rather than tagged PDFs. The podcast feed includes full transcripts on each episode page, but the audio player itself relies on the browser's native <audio controls> element — accessibility varies by browser.

Assistive technologies tested

We routinely test against:

  • VoiceOver on macOS (latest Safari)
  • NVDA on Windows (latest Chrome and Firefox)
  • Keyboard-only navigation across all interactive surfaces
  • WCAG 2.1 AA automated checks (Lighthouse + axe-core)

We do not currently include a public Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR). These artifacts will be produced as part of the independent third-party audit referenced above.

Reporting an accessibility issue

If you encounter a barrier using TrustFirst, please tell us. We treat accessibility reports as priority bug fixes and aim to respond within one business day.

Email accessibility@trustfirst.turntwo.dev

When reporting, please include: the URL or feature where you hit the barrier, the assistive technology you're using, and (if possible) what you expected vs. what happened. Screenshots or screen-recordings help but are not required.

Standards we reference

  • Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — w3.org/TR/WCAG21
  • Section 508 of the U.S. Rehabilitation Act (federal procurement)
  • Americans with Disabilities Act (ADA) Title III commercial accommodations
  • EN 301 549 (European public-sector procurement)

Changes to this statement

We will update this page when our conformance status, known limitations, or reporting process change. Substantive updates are timestamped at the top.

For general questions about TrustFirst, visit our Help & contact page.