§ 01Accessibility statement

Accessibility statement

We build eigenvector.group to WCAG 2.2 level AA. This statement records what is built into the pages today, names the testing that has not been done, and sets out what happens when you tell us something does not work.

Last updated 26 August 2026

The standard we build to

This website is built to meet the Web Content Accessibility Guidelines 2.2 at level AA. That is the target for every page, every field note and every document published here.

No public sector accessibility rule applies to a private firm's website. We hold this one to the standard anyway. A document a client cannot read is a document we have not delivered.

What is built into the pages

Each of the following is true of the site as it stands today.

  • A skip link is the first focusable element on every page
  • Focus is visible on every control. The focus ring sits at a contrast ratio of 11.45:1 against the page surface
  • Every form field has a permanent visible label. The label is not a placeholder and does not disappear when you type
  • Errors are described in text beside the field they belong to, and summarised at the top of the form with each line linking to its field. Nothing you have already typed is cleared when an error comes back
  • The site reflows to a 320 CSS pixel width, which is a 1280 pixel window at 400 per cent zoom, without horizontal scrolling
  • Motion respects the prefers-reduced-motion setting. Nothing on the site moves, flashes or plays on its own in any case: there is no carousel and no autoplay
  • Contrast was computed from the palette rather than judged by eye. The lowest text combination on the site is 4.61:1 against its background, and the border on every interactive control is at least 3.37:1
  • Headings are real headings, in order, and every section carries one that names it
  • Every image carries alternative text, and the automated audit run against each build reports any that does not

What has not been tested

Three things a complete statement would normally claim, and this one cannot.

  • No screen reader testing has been done. The pages have not been driven with a screen reader on any platform, so we do not know how they sound. The semantics, the labels and the heading order are correct in the markup, which is not the same thing, and we will not present it as the same thing.
  • No high contrast or forced-colours testing has been done. The palette carries computed contrast ratios, but the site has not been opened in a high contrast mode to see what survives it.
  • No independent audit has been carried out. Everything in the section above was checked by the people who built the site. When an audit has been done, this statement will say so, name who did it, and list what it found.

These are gaps in the testing rather than known defects. We are not aware of a failure in any of the three areas, and we have not looked hard enough to say there is none. A report from someone using this site closes that gap faster than anything else available to us.

One known limit

The service level table on the services page scrolls sideways inside its own frame at narrow widths rather than reflowing to one column. The frame is a labelled region that takes keyboard focus, so it can be scrolled without a pointing device. The same commitments are stated in prose on the same page, and in the master services agreement itself.

How the site is checked

An automated audit runs over every page on each build. It checks internal links and anchors, duplicate ids, heading order, image alternative text, landmark structure and the skip link, and nothing is published while it reports a failure. Contrast ratios are computed from the palette tokens and recorded against the surfaces each token is permitted on.

Automated checking finds a fraction of what matters. That is the reason the section above it is written as plainly as it is.

Telling us about a barrier

Write to enquiries@eigenvector.group with Accessibility in the subject line. It is the only route: no second mailbox, no telephone number, no form to fill in.

Tell us the address of the page and what happened. A description such as "the second link in the header does not take focus" is enough. You do not need to name the standard or the criterion.

Every report is acknowledged within one working day and answered within 10 working days by a named person. Where the fix is small it is made inside that time. Where it is not, the answer sets out what the fix requires and when to expect it. If the answer does not satisfy you, reply to it quoting the reference number, and a member of the firm's leadership reads it.

Alternative formats

Any document on this site is available as large print, plain text or accessible HTML, at no charge, within 5 working days of the request. Ask at enquiries@eigenvector.group.

How this statement was prepared

This statement was prepared on 26 August 2026 by the people who built the site. It records what the build does and names what has not been tested, rather than leaving the gap for you to find. It is reviewed each quarter and whenever a page is added, and it will be rewritten the first time someone outside the firm tests this site.