Policies
Accessibility
Last updated: Draft for review
We build with accessibility in mind on our own site and on the websites we deliver. This page describes what that means in practice and how to tell us when something falls short.
This document is a working draft prepared for legal review. It describes how Havelin actually operates, but it has not been reviewed by an attorney and is not legal advice.
Our approach
We aim to follow widely accepted accessibility practices aligned with WCAG 2.1 AA as a working target: semantic HTML structure, meaningful headings, descriptive alternative text for images, sufficient colour contrast, visible keyboard focus, labelled form fields and clear error messages.
We describe our work as accessibility-conscious rather than certified. We have not obtained a formal conformance audit, and we will not claim one we do not hold.
Client websites
Websites we build follow the same structural practices. Some accessibility outcomes depend on the content a client supplies — for example alternative text quality for uploaded photos, or the readability of client-provided documents. We flag these during onboarding.
Third-party tools a client chooses to embed, such as certain booking or payment widgets, may have accessibility characteristics outside our control.
Reporting a barrier
If any part of this site or a site we built is difficult to use with assistive technology, please tell us through the support form. Include the page and what happened. We treat accessibility reports as priority fixes within our care scope.