Accessibility

Accessibility is part of the build, not an add-on

Every site we build is made to be used with a keyboard, a screen reader, a magnifier or a phone held close to the face. This page says what we do, how it is checked, and — because it matters more than the claim — what is not finished yet.

The standard we build to

  • WCAG 2.1 Level AA is the target for vetrosoft.com and for every site we build for a customer.
  • That is the level referenced by the European Accessibility Act and by accessibility law in the UK and Ireland, which is why we use it rather than a standard of our own.
  • Every page is tested automatically with axe-core, in a real browser, at desktop and phone widths, before it is published.
  • Keyboard reachability is tested separately, because automated tools cannot judge it.

What this means in practice

On every page we publish

  • A “skip to main content” link, so a keyboard user is not made to walk the whole menu on every page
  • A visible focus outline on everything you can reach with Tab
  • Text contrast of at least 4.5:1, checked rather than assumed
  • Real headings in order, so a screen reader can jump through the page
  • Links underlined in body text, not distinguishable by colour alone
  • Regions that scroll are reachable with a keyboard
  • Form fields with real labels, not placeholder text pretending to be one
  • Images carry alt text, and decorative ones are hidden from screen readers

Honest limits

  • Automated testing catches roughly a third to a half of real barriers. It is a floor, not a guarantee.
  • We have not yet completed a full audit with users of assistive technology. That is a real gap and we are not going to describe it as anything else.
  • Customer sites contain customer content. If an owner uploads an image we cannot describe, or an untagged PDF, we flag it — but we cannot fix what we are not given.
  • Third-party embeds — maps, booking widgets, payment pages — are only as accessible as their providers make them.
  • Our partner and admin dashboards are held to the same standard, but they have had less testing than the public pages.

If something does not work for you

  • Write to [email protected] and tell us what you were trying to do and what got in the way. You do not need to know the technical name for it.
  • Tell us what you use — screen reader and browser, magnification, keyboard only — if you are comfortable saying. It makes the problem far quicker to reproduce.
  • We aim to reply within 5 working days and to tell you either that it is fixed, or when it will be.
  • If a barrier stops you completing something on a site we host, we will give you another way to do it while it is being fixed.

This statement describes the state of the site on the date it was last reviewed. We would rather publish a short honest list of gaps than a long claim we cannot evidence — an accessibility statement that overstates is worse than none, because it tells a disabled visitor not to bother asking.

Report an accessibility problem

We treat these as bugs, not as feedback.