Structure
Landmarks, one primary heading, ordered heading levels, lists, tables with headers and descriptive page titles support orientation.
Accessibility statement
Features, known limits and practical testing used to make the publication easier to perceive, navigate and understand.
Private client preview · legal operator details pending client confirmation
Keyboard
Skip links, visible focus, native controls and a trapped first-entry modal support navigation without a pointer.
Visual access
Responsive type, high-contrast ink and cobalt, non-colour labels, reflow and horizontal table containment support zoom and smaller screens.
Motion and media
Reduced-motion preferences are respected. Decorative graphics use empty alternative text; substantive meaning is also available as text.
Accessibility is maintained, not certified
The project aims toward WCAG 2.2 AA practices where applicable, but does not claim certification or full conformance. Automated tools catch only some barriers; production release needs manual and assistive-technology checks.
First-entry modal behaviour
When shown, focus moves into the labelled modal, background scrolling stops, Tab and Shift+Tab remain within it, and focus returns to the prior element after acknowledgement. The dark translucent backdrop uses blur while preserving modal contrast.
Current limitations
- Dense financial tables can require horizontal scrolling on narrow screens.
- Wide formulas and third-party source documents may not reflow consistently.
- Screen-reader combinations have not yet been comprehensively tested.
- No monitored feedback route or alternative-format service is active in the private preview.
- Content readability can still be affected by unavoidable technical market terminology.
Checks before public launch
The release checklist includes keyboard-only navigation, focus order, 200% and 400% zoom/reflow, text spacing, contrast, page-title and landmark checks, accessible-name inspection, reduced motion, automated validators and spot checks with current desktop and mobile screen readers. Results should record browser, operating system, assistive technology and date.
Reporting a barrier
Once a monitored channel is confirmed, reports should include the URL, attempted task, barrier, browser/device and assistive technology where relevant. Do not send sensitive financial or identity data. Response arrangements will be published only when operational.
Review date and responsibility
Statement reviewed 30 July 2026 for the private preview. Accessibility ownership, contact route and remediation workflow remain launch dependencies pending legal operator confirmation.