Vidyom wants this website to be usable by everyone, including people who navigate by keyboard, use a screen reader, or prefer reduced motion. This statement describes what we build for accessibility today, the standard we work toward, and the limitations we are honest about. Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — we treat that as a target we work toward, not a certification we claim.

1. Our target

We aim to conform to WCAG 2.2 Level AA. This is a goal we are actively working toward, not an audited certification. We build with these guidelines in mind and improve the site as we find and fix gaps. Accessibility is an ongoing effort, so parts of this site will meet the target more fully than others.

2. Keyboard navigation

The site is built to be operated without a mouse. Every page starts with a “Skip to content” link, so a keyboard user can jump straight past the header navigation to the main content instead of tabbing through it on every page. Links and interactive controls are reachable in a logical order and show a visible focus state, and the site content is real HTML rather than a canvas or image, so it responds to normal keyboard interaction.

3. Reduced motion

The site uses animated diagrams to explain the product, but every animated element respects the operating-system “reduce motion” setting. When you have reduced motion turned on, the scroll-reveal effects and the moving diagrams stop animating and degrade to a static, legible frame — you see the same information without movement. Motion is decorative here, never the only way to read something.

4. Text alternatives for animated diagrams

The animated visuals on the site (for example the live-ledger and onboarding diagrams) are marked up as a single image with a text description: each carries role="img" and an aria-label that summarises what the diagram shows, so a screen reader announces the meaning rather than reading out every moving part. The purely decorative inner pieces of those diagrams are marked aria-hidden so assistive technology skips the visual noise and hears only the summary.

5. Semantic HTML and headings

Pages are server-rendered as real text and semantic HTML — headings, lists, links and landmark regions (including a single main landmark that the skip link targets). Because the content is real text rather than script-generated, the core pages remain readable and navigable even with JavaScript disabled. A clear heading structure lets screen-reader and keyboard users move through a page by its sections.

6. Colour and contrast

Colours come from the shared Vidyom design-system tokens rather than being hand-picked per page, which keeps text and interface colours consistent across the site. We work toward the WCAG 2.2 AA contrast levels and do not rely on colour alone to convey meaning — status and emphasis are also carried by text and shape. If you find a specific place where contrast is too low, please tell us (see below) and we will fix it.

7. Known limitations

We would rather be honest than overstate our conformance. Current limitations we are aware of:

Some of the richer animated diagrams are decorative and are summarised by a single aria-label; the full step-by-step detail they illustrate in motion is not always exposed as separate text.
Third-party embeds are kept to a minimum, but where present (for example anonymous analytics) their accessibility is not fully under our control.
We have not completed a formal, audited WCAG 2.2 AA conformance review, so some issues may remain unfound until reported or discovered.

8. Reporting an accessibility problem

If you hit a barrier on this site — something you cannot reach with a keyboard, a diagram with no useful text alternative, low-contrast text, or anything else — please tell us. Email us at [email protected] and describe the page and the problem. We aim to acknowledge accessibility reports within 5 business days and to work with you toward a resolution or a reasonable alternative way to get the information you need.