Accessibility Statement

1. Our commitment to accessibility

QuarterCharts is committed to making financial-data visualization usable by everyone, including people who rely on assistive technologies. We design the site to be perceivable, operable, understandable, and robust — the four guiding principles of the Web Content Accessibility Guidelines (WCAG).

Accessibility is part of how we build, not a one-off audit. New features ship with keyboard-navigable interactions, semantic markup, sufficient colour contrast, and meaningful text alternatives where possible.

2. Conformance status

QuarterCharts targets WCAG 2.1 Level AA conformance across the site's public pages and authenticated dashboard. WCAG 2.1 AA is the de-facto global baseline for consumer-facing web services (referenced by ADA settlements in the United States, the European Accessibility Act, AODA in Ontario, and the UK Public Sector Bodies Accessibility Regulations).

We undergo periodic internal audits and address findings as part of the regular release cadence. We do not currently publish a third-party audit certificate.

Next scheduled review: 2026-11-23.

3. Known limitations

We aim to be honest about gaps. The following areas of QuarterCharts have known accessibility limitations that we are actively working to address:

• Chart visualizations: Sankey diagrams, multi-statement charts, and per-ticker fundamental dashboards are rendered as SVG with some interactive surfaces (hover tooltips, click-to-drill). Screen-reader narration of the underlying time-series values is partial — the chart caption + tabular data presentation in the same page section serves as the equivalent textual experience. Full per-data-point ARIA narration is a roadmap item.
• Embedded third-party content: Some pages embed company-logo imagery sourced from third-party providers. Alt-text is provided for the company name; the visual brand mark itself is decorative.
• Dynamic toast notifications: Some success / error toasts (e.g. after saving a watchlist entry) auto-dismiss after a short interval. We pair these with persistent inline status messages for users who need more time to read, but the auto-dismiss timing itself may not meet WCAG 2.2.1 ("Timing Adjustable") in every case. Operators of assistive technologies that announce live regions will receive the message regardless of the visual dismiss timing.
• Colour-only conveyance in dense data tables: A small number of table cells use colour as a primary signal (e.g. positive vs negative YoY deltas). These are always paired with a leading sign character (`+` / `-`) and a numeric value, so the meaning does not rely on colour alone, but the redundant text labelling could be made more explicit in some places.

If you encounter an accessibility barrier not listed here, please tell us — see the feedback section below.

4. Compatibility

QuarterCharts is designed to work with the following assistive technologies, used in combination with a modern, evergreen browser (current and previous major versions of Chrome, Firefox, Safari, and Edge):

• VoiceOver on macOS and iOS.
• NVDA on Windows.
• JAWS on Windows (recent versions).
• TalkBack on Android.
• Browser-native zoom up to 400%.
• Operating-system-level high-contrast and reduced-motion settings.

5. Technical specifications

QuarterCharts relies on the following web technologies: HTML5, ARIA, CSS, and JavaScript (server-rendered React with progressive hydration). JavaScript is required for some interactive features (chart drill-down, ticker search, authenticated dashboard). Core read-only views — the rendered charts, sankey diagrams, and text content — are server-rendered and accessible without JavaScript.

6. Feedback

We welcome feedback on the accessibility of QuarterCharts. If you encounter a barrier, find an error in this statement, or have a suggestion for improvement, please email feedback@quartercharts.com with the subject line “Accessibility” and as much detail as you can share (the page URL, the assistive technology and browser you were using, and what you expected to happen versus what happened).

We aim to acknowledge accessibility feedback within five business days and address actionable issues in subsequent releases.

7. Related

See also our Privacy Policy, Terms of Service, and contact page.