Accessibility Statement

We want everyone to be able to use Orchard72, including people who rely on assistive technologies such as screen readers, keyboard-only navigation, screen magnification, or speech-recognition software. This statement explains the accessibility standard we work towards, where we currently fall short, and how you can tell us about a problem so we can put it right.

1. Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines, published by the World Wide Web Consortium, explain how to make web content more accessible to people with a wide range of disabilities. Level AA is the level most commonly referenced by accessibility legislation.

We have not yet commissioned an independent, formal accessibility audit, so we describe our position as partially conformant: most of the platform is designed and built with these guidelines in mind, but some content or functionality may not yet fully meet them. We treat WCAG 2.1 AA as a target we are actively working towards rather than a certification we claim to hold.

We name version 2.1 because that is the version our own accessibility checks are configured to test against. If we widen those checks, we will move the target stated here with them, rather than claim a standard we do not test.

2. What we have done

Accessibility is considered as part of how we build the platform. Steps we take include:

• using semantic HTML and ARIA attributes so that page structure, headings, form labels, and interactive controls are exposed to assistive technologies;
• supporting keyboard navigation and visible focus states for interactive elements;
• designing for readable colour contrast and offering a dark theme;
• using responsive layouts that adapt to text resizing and different screen sizes; and
• providing text alternatives for meaningful images.

3. How we test, and what the testing found

We run automated accessibility checks against a running build of the platform, using the axe testing engine configured to the WCAG 2.0 and 2.1 Level A and AA rules. So that this means something, here is exactly what those checks cover and what they last found.

• Six pages that most people cannot avoid, the home page, pricing, sign in, register, the dashboard and the account area, each checked at a desktop and a mobile width.
• Thirty rules are enforced across those pages, covering the correctness of the accessibility information we give assistive technologies and whether every control has a name that a screen reader can announce. All thirty pass on every one of those pages at both widths.
• Colour contrast is measured on the same pages and reports no failures, but the engine cannot decide every element where backgrounds are layered, so we do not present it as a settled result. We are fixing the elements it cannot decide rather than counting them as passes.

Automated checking finds only a share of real accessibility barriers, and these checks do not cover every page, the documents you download, or the third-party tools we embed. We have not commissioned an independent audit, so please do not read the result above as a claim that the platform is free of barriers. It is a floor we hold ourselves to, and the reason we ask you to tell us what we have missed.

4. Known limitations

We are aware that parts of the platform do not yet fully meet our target. Known areas where you may encounter difficulty include:

• some complex, multi-step flows (for example parts of the will-generation wizard) may not be fully optimised for every assistive technology;
• a small number of interactive components and third-party embeds (such as video consultations and document viewers) may have gaps in keyboard operation or screen-reader support; and
• some documents you generate or download may not yet be fully tagged for accessibility.

We are working to address these areas over time. This list is not exhaustive, and we update it as we learn more.

5. Reasonable adjustments

Under the Equality Act 2010, we have a duty to make reasonable adjustments so that a disabled person is not put at a substantial disadvantage in using our service. That duty is anticipatory: it is owed to disabled people generally and we are expected to plan for it in advance, which is what sections 2 and 3 above describe. It also applies to you as an individual, so if the way we do something does not work for you, ask us and we will look at changing it for you.

That includes giving you information in a different format. If a document, a form, or any part of the platform is not usable for you, we will look at providing the same information another way, for example as accessible text, in large print, or over a different channel.

We do not charge for an adjustment. The law does not allow us to pass the cost of meeting this duty on to you, and we do not.

To ask for an adjustment or an alternative format, use the contact form and tell us what you are trying to do and what would work better for you. You do not need to explain your disability or provide evidence of it.

6. Giving us feedback

If you come across an accessibility barrier on Orchard72, or you need information from us in a different format, we would like to hear from you. Please use the contact form and let us know:

• the page or feature where you experienced the problem;
• what you were trying to do; and
• the assistive technology, browser, or device you were using, if you know it.

We aim to acknowledge accessibility feedback within a reasonable time and to keep you informed about how we are addressing it. If you are not satisfied with our response, you can raise it through our Complaints Procedure.

7. Regulatory context

In the United Kingdom, the Equality Act 2010 is the law that applies to us, and section 5 above sets out what it means in practice. No United Kingdom law requires a private business to meet a particular technical standard for its website, so WCAG 2.1 AA is a target we have set ourselves rather than one imposed on us. The accessibility regulations that do name a standard apply to public sector bodies, which we are not, although we have adopted the same target they use.

We are also aware of the European Accessibility Act, which has applied since 28 June 2025 to certain products and services offered to consumers, and of accessibility expectations in other regions in which we operate. We treat these developments as part of our ongoing commitment to improve accessibility. This statement describes our current position and does not represent a formal declaration of conformity or a claim to hold any accessibility certification.

8. Related policies

This statement should be read together with our Terms of Service, Privacy Policy, and Disclaimers.