Accessibility Statement

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the standard most accessibility law in the United States points at, and it is the target we build against.

We do not use an accessibility overlay or a plug-in widget. Those are marketed as a one-line fix and frequently make things worse for the people they claim to help. We would rather fix the actual page.

It covers the pages of this website: the home page, the two plan pages, checkout, the customer dashboard and questionnaire, the custom-project enquiry form, and these legal pages.

Two things it does not cover, and it is worth being clear about both:

• Website previews. When you open a preview link, you are looking at a draft of a customer's website — a different site that happens to be served through this one. It is a work in progress and it has not been reviewed for accessibility at the point you see it.
• Finished websites we build for other people. See section 05.

Everything on this site works in current versions of the major browsers on desktop and phone. We have not tested every browser, and we have not tested every screen reader — see section 04.

Checked against the live site on July 25, 2026. These are things we have actually verified, not things we intend:

• Semantic HTML and landmarks — real headings, lists, buttons and links, so a screen reader gets structure rather than a wall of divs. The page language is declared, so it is read in the right voice.
• Keyboard operation. Everything that takes an action — every button, link, form field, checkbox and the checkout flow itself — is a native control you can reach and use with a keyboard. Nothing on this site is a clickable box pretending to be a button.
• A visible focus ring. Whatever the keyboard is on gets a bright outline — buttons, links, form fields, checkboxes alike. On buttons and links it appears for keyboard use rather than flashing on every mouse click. In text boxes it shows whenever the field is active, including when you click into it, because anyone typing needs to see where their keystrokes are going.
• Proper page landmarks. The main content of every page is marked up as a landmark, so a screen reader can jump straight to it without reading through the header first.
• Reduced motion is respected. If your device is set to reduce motion, the smooth-scrolling behaviour switches off entirely, and the boxes stop drifting and stop growing when you point at them. This is honoured in the stylesheet and in the components themselves, not just one of the two.
• Decoration is hidden from assistive tech. The background grid, the glow shapes, the ornamental arrows and the 3D shape are all marked so a screen reader skips them instead of announcing them.
• Form fields have real labels, and their hints and error messages are text, not colour alone.
• Status messages are announced. When something saves, sends, fails or finishes uploading, the message is placed in a live region so a screen reader reads it out instead of you having to go hunting for it.
• No time limits. Nothing on this site expires while you are filling it in, and your questionnaire answers are saved as you go.

We would rather list these than let you discover them. These are the parts of this site we consider most likely to cause you trouble today:

• No “skip to content” link. If you navigate with a keyboard, you have to tab through the header links on every page before you reach the main content. Screen readers can still jump straight to the content using the page landmark, so this affects sighted keyboard users most. Tell us if this is getting in your way and we will put it back.
• Muted secondary text. Our secondary grey, used for footer lines, hints under form fields and small print, is deliberately quiet. We measured it and darkened it until it clears the WCAG AA 4.5:1 minimum on both the blue page background and the frosted panels. It clears the bar, but “clears the bar” is not the same as comfortable. If it is hard work to read, tell us and we will raise it further — that is a change we can make in minutes.
• Cards that drift and lift. Boxes on the site move very slightly, as if floating, and grow when you point at or tap them so the writing gets bigger. It is decorative and you never need it to use the site. Turning on reduced motion stops all of it — the drifting and the growing — leaving the boxes still. On phones the movement is already smaller.
• Custom scrolling. The site smooths its own scrolling, which can feel wrong with some assistive tools or an unusual input device. It switches off entirely with reduced motion enabled — which, if scrolling feels strange to you, is the setting to try first.
• Website previews. A preview of a generated website is that website, not this one, and it has not been accessibility-reviewed at the point you see it. See section 05.
• We have not tested with every screen reader and browser combination. If yours behaves badly here, we genuinely want to know — we cannot find it on our own.

This statement covers this site. It does not certify the websites the studio builds for its customers.

We build those with the same practices — semantic markup, keyboard operation, sensible contrast, alt text where you give us the wording. But no audit is performed on a customer site unless one is commissioned, and section 15 of the Terms says plainly that we do not warrant a customer's site complies with the ADA, WCAG or any other standard. What a given website has to meet, and who is responsible for meeting it, is settled by your order and those Terms — not by this page.

If certified conformance matters for your business — and in some trades it really does — say so before you buy, so it can be scoped and priced rather than assumed.

If something on this site stopped you doing what you came to do, email pschlicht12@yahoo.com with “Accessibility” in the subject line. That is a real, monitored address — it goes to one person and that person reads it.

Useful, if you have it: the page you were on, what you were trying to do, and what you were using (browser, screen reader, phone or computer). Not required — a sentence is enough.

We review this page when the site changes in a way that affects it, and we update the date at the top when we do. The list in section 04 is written from our own checks, so it is only as good as our last look.

If you find something on this page that is no longer true, that is worth an email too — a stale accessibility statement is its own kind of barrier.