Veda Software · Policy
Accessibility Statement
How Veda Software approaches accessibility on this website.
We build software for a living, so we hold our own website to the standards we would hold a client system to. This statement describes the accessibility measures already in place, the standard we are testing against, and how to tell us when something does not work for you.
Last reviewed: July 2026
01 · Our commitment
Usable by as many people as possible.
Veda Software wants this website to be clear, readable and operable for as many people as possible — including people who navigate by keyboard, use assistive technology, prefer reduced motion, or rely on strong colour contrast. Accessibility is treated as an engineering requirement, not an afterthought: it is considered when pages are designed, built and changed.
02 · The standard we build to
WCAG 2.2 AA, honestly stated.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA and are testing against it; this statement will be updated as formal testing completes.
We do not currently claim conformance, and the website has not been independently audited or certified. Where testing finds issues, we will fix them or record them honestly in the known limitations below.
03 · What is in place today
Concrete measures, already built.
The following measures are implemented across the website now:
- Semantic HTML — pages use meaningful structure: one main heading per page, a logical heading hierarchy, landmarks, lists and labelled navigation.
- Keyboard navigation— the site can be navigated by keyboard, including a “skip to main content” link at the top of every page.
- Visible focus states — interactive elements show a clear visible indicator when focused.
- Reduced-motion support— animations respect the operating system’s reduced-motion preference and collapse to instant visibility when it is set.
- Contrast targeted at AA — text and interface colours are chosen against WCAG AA contrast thresholds on ivory and purple sections.
- Accessible forms — form fields carry visible labels, and validation messages identify errors in text rather than by colour alone.
04 · Known limitations
Where accessibility may depend on others.
Parts of the experience may rely on third-party tools — for example consent controls, embedded content or external services we link to. Where that happens, accessibility partly depends on those providers. We aim to choose responsible tools and to improve the experience where we can.
As formal testing completes, any issues we cannot fix immediately will be listed here with an honest description and, where possible, an alternative route to the same content or outcome.
05 · Feedback and contact
Tell us what is hard to use.
Feedback genuinely helps us prioritise fixes. If any part of this website is difficult to use, read or navigate — or you would prefer information in another reasonable format — please contact us.
Email hello@vedaai.co.uk with the page URL, a short description of the issue, and the device, browser or assistive technology you were using. We aim to respond to accessibility queries within five working days.
06 · Review of this statement
Reviewed as the site develops.
This statement is owned by Veda Software’s leadership and will be reviewed as formal testing completes, whenever significant new pages or interactive features are added, and at least annually.