Accessibility

Last updated , the date this version of the site was published.

TidySteps wants everyone to be able to read this site and place a pre-order on it, including people who use a screen reader, a keyboard, magnification, high contrast, or who are sensitive to motion. If something on the site is in your way, the fastest fix is to tell us through the contact details shown at checkout.

Standard

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the W3C Recommendation of 12 December 2024. For body text we go past AA: every paragraph on this site is set to meet the Level AAA contrast ratio of 7 to 1 against its background, in both the light and the dark color scheme.

What we have done

Checkout

Payment happens on a page hosted by Stripe, our payment processor. We do not embed it, so its accessibility is Stripe's responsibility under Stripe's own statement. If the checkout page is a barrier for you, tell us through the contact details shown there and we take your deposit by another route at the same price and on the same terms.

Known limitations

None listed at this time. When a barrier is found and cannot be fixed at once, it is listed here with the date found and the planned fix date, and removed when fixed.

How we check

Before each release we check every page template for contrast, keyboard operation and heading structure, in both color schemes, and we fix what we find before the release goes out. A barrier you report is checked the same way.

Tell us about a barrier

Use the contact details shown at checkout, or your pre-order confirmation email if you have placed one, and include the page address and what happened. We reply within 5 business days, and we fix what we can in the next release. If you need any page on this site in another format, or need help placing or cancelling a pre-order, the same route reaches a person who can do it with you.

Contact

Reach TidySteps through the contact details shown at checkout. If you have placed a pre-order, your confirmation email carries the same support contact, and a report sent there is handled the same way.