Accessibility statement

The site aims to meet Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA. We design and build against that standard and re-evaluate as content and features evolve.

The Veengu marketing site is a B2B information site that does not, in itself, constitute a consumer-facing service under the European Accessibility Act (Directive 2019/882). We nevertheless target the same conformance level because regulated-fintech customers run procurement-stage accessibility reviews on suppliers, and because doing so is the right thing.

• Colour contrast — body text, eyebrows, buttons, and UI controls use a colour token set chosen against WCAG AA contrast ratios on the page background. The design system documents the contrast values in src/styles/global.css.
• Semantic landmarks — every page uses <header>, <nav>, <main>, and <footer> landmarks so screen readers can navigate by region. A "Skip to main content" link is the first focusable element.
• Focus rings — keyboard users see a visible 2 px brand-purple outline on every interactive control.
• Form labels and error patterns — every form field carries a programmatic <label>, required-field markers, and inline error rendering. Forms work without JavaScript as a graceful fallback.
• Touch targets — interactive elements meet the 44 × 44 px WCAG 2.5.5 target size on mobile, including the navigation hamburger and consent-banner buttons.
• Responsive layout — content reflows to a single column at ≤ 640 px without horizontal scrolling, font sizes stay ≥ 16 px in body text on mobile, and the cookie banner is reachable on every page.
• Global Privacy Control — the site respects the navigator.globalPrivacyControl signal so users with privacy preferences set at the browser level don't have to interact with the cookie banner.

We have not yet completed a full third-party WCAG 2.1 AA audit. The areas most likely to need additional work, based on internal review, are:

• Decorative diagrams — the bespoke SVG visuals on the case-study pages and several /platform/ subpages are presented as decorative. Some carry meaning that screen-reader users currently miss. We plan to add text descriptions or aria-label equivalents in the next pass.
• Image alt text on legacy content — some long-form blog articles that migrated from the previous WordPress site reference images with empty or generic alt text. We are progressively rewriting those.
• Reduced-motion preference — the cookie banner uses a slide-in animation that does not currently honour prefers-reduced-motion. Tracked for the next iteration.
• Right-to-left content — the site contains incidental Arabic numerals in the Saudi case study but is not currently configured for full right-to-left rendering. Adding RTL support is part of Wave 2.

We will update this list as we audit, fix, and re-test. The presence of an item here does not mean it cannot be used today — it means we know there is room to improve.

The site is tested with the following tools and assistive technologies during development and before significant releases:

• Manual keyboard navigation on every page (no mouse).
• VoiceOver on macOS Safari and TalkBack on Android Chrome for screen-reader spot checks.
• axe-core automated accessibility scans and Lighthouse accessibility audits.
• Responsive checks at viewport widths from 320 px to 1280 px.

If you find an accessibility issue on veengu.com — content you cannot perceive, navigation you cannot complete, a control that does not work with your assistive technology — please tell us at sales@veengu.com. We aim to respond within three business days. Where possible, include the page URL, a short description of the problem, and the assistive technology + browser you are using.

If we cannot fix an issue quickly, we will work with you to find an alternative way to get the information you need.

This accessibility statement applies to veengu.com and was last reviewed on 2026-05-18. It will be reviewed again when there are material changes to the site or at least once every twelve months.