Legal 12

Accessibility Statement

Effective 18 November 2026 · Last updated 18 November 2026 · Version 2026.11.18

Contents (13 sections)
  1. 12.1 Accessibility intention
  2. 12.2 Standard and current status
  3. 12.3 Financial charts and tables
  4. 12.4 Forms and authentication
  5. 12.5 Responsive and reduced-motion access
  6. 12.6 Third-party content
  7. 12.7 Reporting barriers
  8. 12.8 Ongoing improvement
  9. 12.9 Standard and present status
  10. 12.10 Keyboard, focus and navigation
  11. 12.11 Research tables and chart alternatives
  12. 12.12 Animation, media and readable text
  13. 12.13 Reporting and realistic remediation

12.1 Accessibility intention

Dear visitor, INRGIFT aims to provide financial research features that can be understood and operated by people with a broad range of abilities, devices and assistive technologies. We are working toward readable typography, keyboard operability, visible focus, semantic page structure, labelled forms, accessible tables, sufficient contrast and appropriate alternatives for nonessential motion.

12.2 Standard and current status

We use WCAG 2.2 AA as an accessibility design and review target where appropriate. This is a target rather than a certification: a successful production-wide accessibility audit has not yet been established. We will not claim full conformity while keyboard, browser or automated testing remains incomplete. A built page and a screenshot are not a substitute for actual testing.

12.3 Financial charts and tables

Charts, trading-style research terminals and dense financial tables create particular challenges. Where technically possible, important information should remain available in structured text or table form, use units and period labels, avoid conveying meaning through colour alone and support keyboard access to critical controls. Indicators and plotted results should have understandable descriptions or accessible fallback content.

12.4 Forms and authentication

Sign-in, email and phone verification, OTP entry, checkout, account closure, cancellation and grievance forms should communicate errors clearly and offer sufficient time and input assistance. Session-related controls must remain navigable with a keyboard or assistive technology, without sacrificing appropriate security.

12.5 Responsive and reduced-motion access

The service should adapt to small screens and text enlargement without requiring horizontal scrolling for essential actions. Nonessential transitions should respect reduced-motion preferences. Complex research layouts may reorganise elements for usability, but essential data and controls should not silently disappear.

12.6 Third-party content

Embedded charting, authentication, payment or other licensed interfaces may have independent accessibility constraints. We will assess practical alternatives and assistance mechanisms where feasible. A third-party limitation does not justify falsely claiming complete accessibility.

12.7 Reporting barriers

If a feature is difficult to use, contact support@inrgift.com with the subject Accessibility Feedback. Identify the page, device or assistive technology where relevant, and explain the task you were trying to complete. Do not send passwords, OTPs or private payment details. We will triage reports and communicate an available alternative or fix when practicable.

12.8 Ongoing improvement

Accessibility is part of product testing, not merely a legal declaration. We aim to maintain regression checks for keyboard navigation, focus behavior, forms, contrast, screen-reader semantics and responsive layouts as features change. We will revise this Statement when actual testing supports an updated conformance description.

12.9 Standard and present status

INRGIFT aims to design toward WCAG 2.2 Level AA and relevant applicable accessibility obligations, but this target is not a claim of completed certification. Public pages, account forms and interactive research components should have evidence of testing at representative device widths and with keyboard and assistive technologies. Known limitations should be described plainly rather than hidden.

12.10 Keyboard, focus and navigation

Primary navigation, drop-down menus, dialogs, search, account actions and legal links should support keyboard operation, logical focus order, visible focus, accessible names and restoration of focus after modal closure. Interfaces that open only on hover or that trap keyboard focus without escape routes should be corrected.

12.11 Research tables and chart alternatives

Where charts convey important financial quantities, equivalent data and labels should be accessible outside colour-only visuals. Large tables need readable headings, numerical units, appropriate horizontal scrolling and announcements of filtering or sorting. Financial gains/losses should not be distinguished by green/red colour alone.

12.12 Animation, media and readable text

Users with reduced-motion preferences should be able to avoid nonessential animation. Videos should have appropriate captions or a textual alternative where required. Forms must identify errors in understandable language and must not rely on a placeholder as the only label. Small mobile screens must not require horizontal scrolling of ordinary page text.

12.13 Reporting and realistic remediation

Users may report a barrier with the affected route, device/browser, assistive technology and task, without providing passwords or unrelated sensitive information. The company should triage reports, communicate any reasonable alternative, assign ownership and verify fixes. No exact conformance claim should be published without independent evidence.