Accessibility

Statement date: August 26, 2026

Our commitment

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.

The standard we target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 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.

What we have built to meet it

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.

Known limitations, and how to work around them

The line of recent sales is read as text, not as a shape. On a card's page the line beside the last sale is summarized in words (“Last 12 sales, 0.0100 to 0.0118 USDC”), and every sale is listed with its time, coins and price under “Sales table”. What the line still gives that the text does not is its shape at a glance.

Report a barrier

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 legal@veledah.com. We respond to accessibility reports, and confirmed barriers are tracked and scheduled for repair.

How often we review this

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

The standard we target

What we have built to meet it

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.

Known limitations, and how to work around them

The line of recent sales is read as text, not as a shape. On a card's page the line beside the last sale is summarized in words (“Last 12 sales, 0.0100 to 0.0118 USDC”), and every sale is listed with its time, coins and price under “Sales table”. What the line still gives that the text does not is its shape at a glance.