01Our commitment
A veterinary hospital hires people with a wide range of vision, hearing, motor control, and attention. A website that only works for some of them is a badly built website. We treat accessibility as part of the build, not a retrofit.
02The standard we work to
We aim to meet WCAG 2.1 Level AA. That is the level most commonly referenced by US accessibility law and by procurement teams. We have self-assessed against it; we have not commissioned a formal third-party audit.
03What we have done
- Semantic HTML throughout — real headings, lists, landmarks, and form labels, so screen readers announce structure correctly.
- Every interactive element is reachable and operable by keyboard, with a visible focus ring that meets contrast requirements.
- Text and interface colours are checked against their backgrounds for AA contrast, in both light and dark appearance.
- The page respects the operating system light and dark setting, and respects prefers-reduced-motion — animation, the message thread, and scroll reveals all stop for anyone who has asked for less movement.
- Photographs carry descriptive alternative text. Decorative graphics are hidden from assistive technology.
- Layout is responsive and reflows to 320px without horizontal scrolling, and text can be zoomed to 200% without loss of content.
- Form fields have persistent visible labels, not placeholder-only labels, and errors are announced rather than shown by colour alone.
04Known limitations
- The animated support conversation on the home page plays automatically. It stops for reduced-motion users, but there is no pause control for everyone else. [planned fix]
- The logo scroller in the software strip pauses on hover but has no explicit stop button.
- We have not yet had the site tested by users of assistive technology. [planned]
05Third-party content
Typefaces are served by Google Fonts. If a font fails to load, the page falls back to system fonts and remains fully readable.
06Tell us what is broken
If any part of this site stops you doing what you came to do, email [hello@yourdomain.com] and describe what happened and what you were using. We treat accessibility reports as faults, not feature requests, and we will tell you what we are doing about it and when.