Accessibility Statement
We want as many people as possible to be able to use this website. This page explains the standard we build to, what we have tested, what we know is not right yet, and how to reach us if something here does not work for you.
The standard we build to
This website is built to meet the Web Content Accessibility Guidelines version 2.2 at level AA, which is the recognised international standard. In practice that is meant to mean you can move through the whole site with a keyboard, read it with a screen reader, zoom to 400 per cent without losing content, and read every piece of text at a contrast the standard accepts. Images that carry meaning have text descriptions, and purely decorative ones are skipped by screen readers rather than announced.
Display options, and why this site has them
There is a Display options button in the corner of every page, and another at the bottom of this one. It opens a small panel of settings that change how this site looks on your device: text size, more space between lines and letters, a simpler typeface, higher contrast, solid rather than frosted panels, a stronger outline around whatever you have selected, underlined links, less movement, and larger areas to tap.
We added it because the standard this site is built to sets one appearance that has to work for everybody, and no single appearance does. Someone reading on a phone in bright sun, someone whose eyes tire by the afternoon, someone who finds animation uncomfortable, and someone using a keyboard rather than a mouse all need something slightly different from the same page. Rather than guess which of those you are, we let you say.
It is likely to help if you have low vision, if you read more comfortably with more spacing or a plainer typeface, if movement on screen makes you feel unwell, if you navigate by keyboard and lose track of where you are, or if a hand tremor makes small buttons hard to hit. You do not need any of those reasons to use it. If a setting makes this site easier to read, that is reason enough.
Your choices are remembered on the device you are using, in your browser's own storage. Nothing is sent to us, and we cannot see what you have set. The panel has a Reset all button that removes the record entirely.
What this panel is not. It is not an accessibility overlay, and it is not what makes this site accessible. It changes nothing about the underlying page: it does not alter what a screen reader announces, it does not add descriptions to images, and it does not change how anything is coded. The accessibility of this site is the work described in the rest of this statement, and it has to stand on its own with every one of these settings switched off. If this panel were ever the answer to whether the site is accessible, the answer would be no.
These settings also do not replace the accessibility settings built into your own browser, phone or computer. Those apply to every site you visit and can usually do considerably more than we can, including magnification, screen readers and system wide colour changes. If you rely on those, this site is built to work with them.
What we know is not right yet
We would rather name these than claim a clean sheet that five minutes of testing would disprove.
- We have not yet tested with a screen reader. The site is built with ordinary headings, lists, buttons and links rather than custom widgets, which is the thing that usually goes wrong, and the checks we have run are listed below. But a screen reader pass has not been done, so we are not claiming one. It is scheduled before the end of September 2026.
- We have not yet tested at 400 per cent zoom. The layout is built to reflow and we have no reason to think it fails, but we have not sat down and checked it, so we are not saying we have. Scheduled alongside the screen reader pass.
- The logo sits taller than the header bar. At some window sizes it overlaps the edge of the bar. It is a visual fault rather than a barrier, and it does not affect the link itself, but it is untidy and it is on the list.
- One page, the second page of the blog listing, is empty. It has no heading and does not declare its language, which would make it confusing to reach with a screen reader. It is hidden from search engines and nothing on the site links to it, and it is on the list to be removed.
- Some of our written content is dense. Information security is a jargon-heavy field and we work hard to keep it plain, but some pages are longer and more technical than they need to be. If a page is hard going, tell us and we will rewrite it.
If you find something that is not on this list, please tell us. We would rather know.
If you need something in a different format
If you need anything on this site in another format, for example large print, plain text, or read out to you over the telephone, contact us and we will provide it. Tell us what format suits you and we will do our best to get it to you within 5 working days.
Telling us about a problem
If there is something on this website you cannot use, please email info@vinula.co.uk or call +44 7510 403140. Tell us which page it was and what happened. We will reply within two working days, even where the fix itself will take longer, and if you were trying to get information we will send it to you another way straight away rather than making you wait for the site to be corrected.
How this site was tested
This site was last checked on 12 August 2026 by Begin Group Ltd. This is what was actually done, so you can judge how much weight it carries:
- An automated check of all 31 pages of the site, covering heading order, one main heading per page, text descriptions on images, labels on every form field, the page language, and whether every link says where it goes. One page failed and it is named above.
- A keyboard check of the order things are reached in, the skip link, and the cookie banner and its settings panel. Focus is shown everywhere, the order follows the page, the banner is the second thing reached rather than the last, the settings panel keeps focus inside it while it is open, and Escape closes it as a refusal and puts focus back where it was.
- A colour contrast check of the cookie banner, the footer and the keyboard focus indicator, measured against the ratios the standard sets. The focus indicator failed on the white parts of the site and was changed to a two-colour ring that passes on both the light and the dark backgrounds.
Two checks in our process were not carried out: a screen reader pass, and a reflow check at 400 per cent zoom. Both are in the list of known issues above rather than glossed over. Colour contrast was measured on the parts of the site changed on this date, not on every element of every page.
Changes to this page
- 12 August 2026: first published.
Last updated 12 August 2026.
