Accessibility Statement

We want this site to be usable by everyone, including people who browse with a screen reader, navigate by keyboard, or rely on magnification and high contrast. This page states what we're aiming for, what's built in, and what we know is still outstanding.

The standard we work to

We use the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our target. It's the benchmark most commonly applied to websites in the United States.

To be precise: this is a statement of intent and ongoing effort, not a claim of full conformance. Parts of the site have not been formally tested yet, and those gaps are listed below. We'd rather describe the site accurately than overstate it.

What's built in

Accessibility was part of how this site was built rather than something retrofitted afterwards. What that means in practice:

• The content works without JavaScript. Every specification, price, FAQ answer and form field is in the delivered HTML, so you can read and understand the whole offer with scripting turned off. Sending the quote form is the one exception — see the limitations below.
• A “Skip to content” link is the first thing you reach by keyboard, and each page has a single main landmark.
• Semantic HTML throughout — real headings in order, real links, real buttons, real form labels.
• A visible keyboard focus indicator on every interactive element, designed to stay visible on both light and dark backgrounds.
• Anything hidden from view is also removed from the keyboard tab order, so focus never lands on something you can't see.
• The mobile menu closes with the Escape key, and falls back to plain visible links if JavaScript doesn't load.
• The FAQ uses native expand/collapse elements, so it works with a keyboard and is understood by assistive technology without custom scripting.
• Quote form: every field has a real label; required fields are marked with a symbol and explained in words, never by colour alone; errors appear as text beside the field they belong to, are announced to screen readers, and move keyboard focus to the first problem.
• Text and interface colours were chosen against the WCAG 2.1 AA contrast thresholds, including a minimum contrast for form field borders.
• The layout survives a narrow window and larger text. Every page reflows to a 320-pixel-wide viewport — the width WCAG 1.4.10 specifies, which is what 400% zoom produces on a typical laptop — with no sideways scrolling. Applying the text-spacing WCAG 1.4.12 asks for on top of that (taller lines, wider letter, word and paragraph spacing) clips nothing and adds no sideways scrolling either. Both were measured on all four pages rather than assumed.
• The hero text over the photograph was measured, not estimated. Because that text sits over a picture rather than a flat colour, the contrast was checked by sampling the actual pixels behind every line, at fourteen screen widths from 360 to 1920 pixels. Every line clears the AA threshold at every one of them. The specification line under the headline used to be set in a mid-tone blue that fell below the threshold on narrow screens; it is now white, and the shortfall it caused is gone rather than disclosed.
• Images carry text alternatives and fixed dimensions, so the layout doesn't shift as the page loads.
• Motion respects your system's “reduce motion” setting. Nothing on the site moves, flashes, or auto-advances on its own.
• Page zoom is not blocked, and there is no audio or video requiring captions.

How the site is built

It's a static HTML site targeting current versions of Chrome, Safari, Firefox and Edge. Systematic testing across browsers and assistive technologies is ongoing rather than complete, which is why the limitations below are stated plainly.

Known limitations

We'd rather name these than leave you to find them:

• No formal screen-reader testing yet. The site is built to established practice and checked in code, but has not been through a structured test pass with VoiceOver, NVDA or JAWS.
• Some touch targets may be under 24 pixels. A few compact labels and footer links may fall below the WCAG 2.2 minimum target size.
• Gallery video has no captions or audio description. The clip in the gallery is a few seconds of silent footage with no speech and no audio track at all, and its text alternative is in the page. It does not start on its own.
• Sending the quote form requires JavaScript. You can read every field with scripting off, but the form cannot be submitted that way, because the anti-spam check it depends on runs in the browser. If that affects you, our phone number is a plain link in the header, the quote section and the footer, and it works with scripting disabled — call and we will take your details directly.
• Anti-spam check. The quote form uses Cloudflare Turnstile, a third-party service we don't control. It's designed to work without solving a visual puzzle, but it isn't a component we can fully audit.
• Third-party resources. Fonts are served by a third party whose accessibility we can't guarantee.

Tell us about a problem

If any part of this site stops you getting the information you need, we want to hear about it — and we'll get you the information another way while we fix it.

For anything wrong with the website itself, the quote form is the fastest route. It reaches Ages Productions, who build and maintain this site and are the people who can change it. It helps if you can tell us the page, what you were trying to do, and the browser and assistive technology you were using.

The phone number on this site goes to Clever Productions & Entertainment, who fulfil the rental — delivery, setup and onsite services. Call (305) 767-4621 for anything about the rental itself, and for a quote if the form is the obstacle. Messages about the website are passed on to us, but that is the slower way round. If a voice call is not a route you can use, dial 711 to reach that number through the free telecommunications relay service, which handles the call in text on your side and speech on theirs.

We are a small operation, so we are not going to promise you a turnaround we might not meet. What we will do is get you the information another way while we look at fixing whatever got in your way.

Keeping this current

We revisit this statement whenever we make significant changes to the site, and whenever someone tells us that something here got in their way. We are not going to put a review calendar on it that we might not keep to — what matters is that the page describes the site as it actually is, and that we fix what we find.