Accessibility statement

Approach

Rail aims to make the payment journey understandable through text, controls, and clear states as well as animation. Payment actions do not require completing a cinematic scroll sequence or interacting with a 3D object.

Keyboard navigation

Use Tab to move between links and controls. A visible focus indicator identifies the active control. Skip links provide a route to the primary content or workspace controls.

The introduction includes chapter controls. Interactive 3D views provide arrow-key controls for perspective, with Home returning to the default view. The payment forms and activity record remain available independently of those views.

Motion preferences

When the device’s reduced-motion preference is enabled, the introduction uses a reading layout and the transaction engine provides a static stage view. This preference can be changed while the page is open. The introduction and engine also provide controls for pausing animation.

Preview and replay controls are optional. They do not authorize or execute a payment.

Rendering alternatives

If 3D rendering is unavailable or interrupted, the interface provides a fallback and a recovery option. Payment details, service messages, and form controls remain textual. A completed payment is communicated through the confirmed response rather than visual effects alone.

Mobile and reading experience

The documentation adapts to narrower screens. Document headings, section links, and standard navigation support reading without a 3D-capable device. Where records extend beyond the available width, the relevant region can be scrolled.

Known limits

This statement describes features implemented in the current interface. It is not a claim of independently verified conformance with an accessibility standard. Device, browser, assistive-technology, and connected-service behavior can vary and require continued testing.