Accessibility

veledah is committed to making the Service usable by as many people as possible, including people who rely on assistive technology such as screen readers, people who navigate by keyboard, and people with low vision. Accessibility is treated as part of the product's engineering standard, not as an add-on.

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We do not claim full conformance; we are working toward it, and we audit against it. This statement covers the public product surfaces of the Service. Internal administrative tooling and development-only demo controls are outside its scope.

To meet the standard we have implemented, and maintain, the following:

• Semantic HTML with landmarks, page-level headings, and a skip-to-content link.
• Full keyboard operability, including modal dialogs that move focus in on open, keep it inside while open, close on Escape, and return focus on close.
• Screen-reader labels on all controls, and live announcements for trade confirmations, errors, and other status messages.
• A contrast-checked color palette: all text meets the 4.5:1 minimum and interactive control boundaries meet the 3:1 minimum against their backgrounds.
• Reduced-motion support: animations are disabled when the system requests it.
• Pinch-to-zoom is never disabled, and text can be resized.
• Automated accessibility scanning with axe-core in the test suite, run against every key page and the open trade dialog, plus manual keyboard testing.

We disclose the following limitations plainly, with the workaround available in each case:

• Chart measurement is pointer-driven. The price chart's drag-to-measure range readout and hover crosshair require a pointer. Equivalent information is always available as text: the 24-hour change, the 1W, 1M, and ALL return figures on each market page, and the chart's own text summary of first-to-last value per timeframe. Keyboard operation of the chart itself is on our roadmap.

If any part of the Service is difficult or impossible for you to use, we want to know. Reports of accessibility barriers may be directed to veledah at [CONTACT EMAIL] or [MAILING ADDRESS]. We respond to accessibility reports, and confirmed barriers are tracked and scheduled for repair.

This statement is dated August 26, 2026 and is reviewed with each release of the Service. The date above reflects the most recent review.