Our commitment and the target
Our target for vadiweb.com is WCAG 2.2 Level AA. That is the standard we design and test against, and the yardstick we accept being measured by.
We are not claiming we have reached it. Conformance is a property of individual pages, not a badge a firm awards itself, and this site has pages of different ages.
Email is our only contact channel, and an enquiry about a five- or six-figure acquisition usually carries information a buyer would rather not repeat. If this site makes that harder for you than for someone else, you lose the representation and we lose the mandate. So this page lists what is broken rather than what is reassuring.
What is built into the site
These are structural choices, not an add-on. There is no accessibility overlay or toolbar here; overlays sit on top of the problems rather than fix them.
- Semantic HTML. Real headings rather than styled paragraphs, exactly one first-level heading on every page, lists marked up as lists, and landmark elements for the header, the navigation, the main content and the footer. Heading order is not clean everywhere yet; that is listed below.
- A skip link. The first thing the keyboard reaches on any page is a link past the navigation to the main content. It is off-screen until it takes focus, then it moves into view.
- Real controls. Links are links and buttons are buttons, so they take focus in an order that follows the visual layout and respond to the keys you would expect. Two places where the keyboard path still breaks are listed below.
- Visible focus. No rule in our stylesheet strips the browser's focus outline from anything you can reach. Where a control draws its own, as the carousel arrows on the home page do, it is at least as visible as the default.
- Colour contrast. Text and interface colours are checked against the AA thresholds, and colour never carries a piece of meaning on its own.
- Alternative text. The only image on the site today is the logo, in the header and in the footer; it sits inside a link and carries the firm's name as its alternative text. Everything else is text. Any informative image we add gets text describing what it conveys, and decorative ones get an empty alt attribute so assistive technology skips them.
- Restrained motion. Motion is decorative and limited to short hover and focus transitions. Nothing autoplays and nothing flashes; the blog carousel on the home page moves only when you press its arrows. The stylesheet does not yet honour a reduced-motion preference, which is listed below.
Known limitations
We do not claim full conformance. These are the barriers we currently know about, stated specifically so you can judge whether they affect you.
Navigation dropdowns open on hover, not on focus
On a wide screen the menus under About, Services, Process, Industries and Insights open when a pointer moves over them. They do not open from the keyboard, and because the closed menu is hidden rather than merely invisible, the links inside are skipped by the tab order entirely. Until we fix the focus handling, every destination in those menus is also linked from its own section index, so the services index, the process index, the industries index and the insights index each list everything beneath them, reachable by keyboard.
The closed mobile menu stays in the tab order
On a narrow screen the menu is moved off-screen when closed rather than removed from the page. Tabbing past the menu button can therefore send focus to links you cannot see, with nothing on screen changing to explain where the focus went. The fix is to take the closed menu out of the tab order.
Smooth scrolling ignores your reduced-motion setting
In-page jumps, including the skip link, animate rather than moving instantly, whether or not your system asks for reduced motion. It is a small fix and it is on the list.
Heading levels are skipped in a few places
A handful of blocks use a fourth-level heading where a third-level one belongs, on the home page and in the footer column titles that appear on every page. Nothing is missing as a result, but anyone navigating by heading level will hit a gap in the outline. We are correcting these as we touch each template.
How we test
Automated checks run against page templates and a sample of pages, covering missing alt attributes, unlabelled controls, low contrast and skipped heading levels. Then a person works through the page: a keyboard pass confirming every interactive element can be reached, operated and left with focus visible, and a screen-reader pass listening to whether the page announces in an order that means anything.
Automated tools catch only a fraction of real barriers, and we would rather say so than let a clean scan imply a usable page. A tool can confirm an alt attribute exists; it cannot tell you the text is useless. Most of what actually stops people is found by a person using the page — the hover-only menus above are an example, since the markup passes a scan and the keyboard does not.