Accessibility Act Ready

Accessibility of this site

23 August 2026

A site that sells accessibility documents and does not publish one has answered the only question that matters about it. This is ours, in the same form we ask of everyone else.

We have not yet published who the controller is. Until we do, treat this notice as incomplete, and do not give us an address: the form that would collect one is switched off for exactly this reason.

Commitment and scope

This statement covers this website, including the scanner, the assessment and the generated documents. It does not cover the Lemon Squeezy checkout, which is a third-party service under its own statement.

How the requirements are met

Known limitations

The scan report can be long. It is grouped under headings so it can be skipped through, but there is no summary view yet, and on a long report that is a real cost to someone navigating by heading.

The generated documents are laid out for print as well as screen. The print stylesheet has been checked by eye and not with assistive technology.

How this is monitored

Our own scanner runs against our own pages as part of the test suite, on every build. Every prerendered page is checked for the markup failures the product reports in other people's sites, and this statement is checked against the Annex V analysis the product applies to other people's statements. A finding on any page fails the build, so a regression cannot be deployed.

That covers what static markup can answer and nothing more. The keyboard, focus and contrast checks in the list above were done by hand and are repeated when the design changes rather than on a schedule; where a change touches the scan form, the assessment or the documents, they are repeated before it ships.

This statement is reviewed whenever either of those checks changes what it would have to say, and the date above is the date of that review.

Report a problem, and where to complain

If anything here stops you doing what you came to do, tell us and say which page and which assistive technology, if any. We will reply and say what we intend to do, including where we do not intend to act and why.

If our answer does not satisfy you, the enforcement authority is the one designated in your own member state, because this Directive is enforced nationally rather than centrally. The authority for each of the nine markets we cover is named on the country pages of this site, and where a member state has not designated one we say so rather than guess.

The standard we used

EN 301 549 and the functional requirements of Annex I to the Directive. We do not claim a presumption of conformity under Article 15, because no harmonised standard has been cited in the Official Journal for this Directive, and that is exactly the point our own product makes.