Accessibility Statement
What we have built into this site, what we know is still missing, and how to book a kit if the site gets in your way. Written plainly, and we would rather list the gaps than claim we have none.
Our commitment
Everyone gets to book their own event.
Recorderly is a small operation selling one thing: camera kits that get shipped to an event and come back as a film. Booking one should not depend on being able to use a mouse, see the screen or hear a video. We build this site to be operable with a keyboard, readable by a screen reader and usable at the text size you prefer, and we fix accessibility defects as ordinary bugs rather than as a separate project.
This statement covers recorderly.com and every page under it, including checkout. It does not cover the internal tools our own team uses.
The standard we aim at
WCAG 2.1 Level AA, without claiming a clean sheet.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the level most public accessibility requirements point to, including the Americans with Disabilities Act as it is commonly applied to websites.
We have not had an independent audit. Our assessment is our own — manual keyboard and screen-reader passes over the pages that matter most, plus browser tooling. So we describe the site as partially conformant: most of it meets the standard, and some of it we have not verified. Saying otherwise would be a claim we cannot back.
What is in place
Specific things, not a list of intentions.
- Every image carries alternative text describing what it shows, so nothing is announced as a filename.
- The site works from the keyboard. Every link, button, form field and the mobile navigation toggle can be reached and operated with the Tab and Enter keys, in the order the page reads.
- Focus is always visible. A high-contrast outline is drawn on whatever element has keyboard focus, sitewide, and we never remove it.
- Every form field has a real label tied to its input, so a screen reader announces what it is asking for. Checkout errors are written next to the field they belong to, in words, not as a colour change alone.
- Motion is optional. The hero clips do not autoplay if your system is set to reduce motion, and animated elements stop under the same setting.
- Videos are silent. The clips on the site are short, muted, looping b-roll with no speech or audio information, and each carries a text description. Nothing is captioned because nothing is said.
- Text scales. Layouts are built in relative units, so browser zoom and larger default text sizes reflow the page instead of clipping it.
- Colour is never the only cue. Selected plans, errors and status states carry text or shape as well as colour.
- Pages declare their language and use ordered headings, so screen-reader navigation by heading works.
- It is built mobile-first and readable at 375px wide without horizontal scrolling.
Where it falls short
Known, current, and being worked on.
- There is no "skip to content" link. Keyboard and screen-reader users tab through the navigation on every page before reaching the content. This is the gap we are fixing first.
- Colour contrast has not been fully verified. Body text and buttons are built for contrast, but some smaller supporting text and the accent colours used on event pages have not been measured against every background they appear on.
- Some interactive blocks have not had a screen-reader pass — in particular the swipeable rows on the homepage, the quantity stepper on the footage-drive page and the region selector on the comparison pages.
- Cost-by-city pages use CSS charts. The figures are stated in text beside them, but the charts themselves are not separately described.
- We have not tested with every assistive technology. Our passes have been with VoiceOver on macOS and iOS and with keyboard-only navigation. We have not tested with JAWS, NVDA or voice-control software.
None of these should stop you booking. If one of them does, section 06 is the way around it and section 07 is how to tell us.
Parts we don't control
Payment fields and fonts.
The card fields on our checkout, balance and footage-drive pages are supplied and rendered by Stripe, our payment processor. They run inside Stripe's own frame, we cannot change their markup, and their accessibility is Stripe's to maintain. Everything around them — labels, headings, errors, the order summary and the pay button — is ours.
Web fonts are served by Google Fonts. If they fail to load, the site falls back to your system fonts and stays readable.
If a payment field is the thing blocking you, don't fight it. Email us and we will take the order and the payment another way — see below.
Another way to book
The site is not the only route.
If any part of this site stops you completing an order, we will do it with you directly. Email orders@recorderly.com with your event type, the date, and a phone number if you would rather talk it through, and a person will take the booking, the shipping address and the payment without you touching the checkout form.
The same goes for anything after the order — checking where your kit is, paying a balance, or asking for a change to your film. There is no step here that only exists on a screen.
Telling us it's broken
We want the report.
If you hit an accessibility barrier, tell us at info@recorderly.com or through the contact form. What helps most: the page you were on, what you were trying to do, and what you were using — browser, device, and any screen reader or other assistive software.
We aim to reply within 5 business days. A fix that is quick goes out the same week; anything larger we will tell you about, including what we intend to do and roughly when.
This statement was last reviewed on 17 August 2026, and we review it whenever the site changes materially. See also our Privacy Policy and Terms of Use.
Stuck on something here?
Email us and we will take the booking with you directly — event, date, address and payment, without the form.