Our approach
Accessibility is treated as part of content quality and product reliability. The goal is to make research, policy information, navigation, and interactive controls usable by as many people as reasonably possible across common browsers, devices, input methods, and assistive technologies.
This statement describes current design practices and feedback channels. It is not a certification and does not claim conformance with a specific accessibility standard or level unless a separate formal audit supports that claim.
Structure and navigation
- Pages use headings, landmarks, links, lists, tables, buttons, and form controls according to their intended function.
- A skip link allows keyboard users to move directly to the main content.
- Policy pages provide an on-page table of contents with links to the sections on that page.
- Link text is written to identify the destination or action instead of relying only on surrounding context.
- Navigation order is intended to follow the visual and reading order.
Keyboard and focus
Interactive controls are intended to be reachable and operable with a keyboard. Visible focus indicators are provided for links, buttons, and expandable controls. Native HTML elements are preferred where they provide reliable keyboard behavior without requiring custom scripting.
If an external widget or third-party service does not provide equivalent keyboard support, that limitation may be outside MindBridge's direct control. An internal text explanation or alternative route may be available where practical.
Text, zoom, and responsive layout
Text is sized for readable desktop and mobile use. Layouts are designed to reflow instead of requiring the entire page to be scaled down. Headings may wrap naturally, tables use contained horizontal scrolling on smaller screens, and page-level horizontal overflow is avoided.
Users should be able to use browser zoom and text enlargement without losing access to the main content. Very large zoom, browser extensions, operating system settings, or third-party widgets can produce differences that require additional review.
Images, charts, and data
Meaningful images include alternative text that identifies their purpose. Decorative images should not create repeated or distracting announcements. Charts and market components may present information visually, so surrounding text should explain the role of the component and any important limitations.
Third-party market widgets may have accessibility behavior determined by their provider. When a market component does not display, the page should provide a clear status and an internal explanation or alternative route rather than exposing internal technical details.
Color, motion, and readability
The visual system uses contrast, spacing, type hierarchy, and focus states to distinguish content and controls. Information should not depend on color alone. Motion is limited and reduced-motion preferences are respected where the page includes transitions or scrolling behavior.
Policy pages prioritize long-form readability over promotional animation. Paragraph length, headings, lists, tables, and callouts are used to organize detailed information without hiding material terms.
Third-party limitations
TradingView, Google Fonts, WhatsApp, browsers, operating systems, and other external services have their own accessibility practices. MindBridge can select, set up, describe, or link to those services, but it does not control every interface, update, or assistive technology interaction provided by a third party.
Report a third-party barrier when it affects access from this publication. The report can help identify an alternative route, implementation change, clearer warning, or provider issue.
Assistance and alternative access
If a page, policy, table, image, or third-party component prevents access to important information, request assistance through the published contact channel. Identify the page, task, device, browser, and assistive technology, and describe the information or action you need.
Where practical, MindBridge may provide a text explanation, a direct internal policy route, a corrected label, a layout adjustment, or another reasonable way to reach the same company-controlled information. An alternative cannot reproduce a third party's entire interface or licensed data feed.
Review and remediation process
Reports are reviewed for severity, reproducibility, frequency, affected task, available workaround, and ownership of the component. A company-controlled barrier can be prioritized for correction. A provider-controlled barrier can be documented, escalated, replaced, or accompanied by clearer internal guidance when feasible.
Accessibility improvements are tested across relevant widths and input methods. No statement on this page is a certification of a particular conformance level.
Report an accessibility barrier
Email and include the page URL, the element or task that was difficult to use, the browser and device, the assistive technology if relevant, and a description of the expected result. Screenshots are helpful when they do not reveal sensitive information.
Accessibility reports are reviewed according to impact, reproducibility, and available remediation. No fixed response or remediation deadline is promised unless applicable law requires one.