Accessibility.

What we’re aiming for

We build this site to meet WCAG 2.2 Level AA, the accessibility standard most of the world’s accessibility law points at.

We’re saying we target it, not that we’ve been independently audited against every criterion. Anyone claiming a perfect score for a site that changes every week is guessing. What we can tell you is exactly how we check, and what we already know isn’t finished.

How we check

• Every page, every deploy. An automated accessibility scan runs against every page on this site — plus the 404 page and opened FAQ answers — on every change. Serious and critical issues fail the build, so they don’t reach you.
• Keyboard and structure. We check that you can reach and operate everything without a mouse, that the focus outline stays visible, and that headings and landmarks describe the page in a sensible order.
• Motion. If your device asks for reduced motion, the entrance animations simply don’t run. Nothing on this site moves on its own, flashes, or autoplays.
• Contrast and zoom. Text is checked against the AA contrast ratios, and the layout reflows down to a phone-width screen without a horizontal scrollbar.

What we know isn’t perfect

Automated tools catch a bit over half of real accessibility problems. The rest need a person, so here’s our honest list rather than a clean one:

• We haven’t finished a full screen-reader pass across every combination of NVDA, JAWS, and VoiceOver. Automated checks and keyboard testing carry more of the weight today than we’d like.
• Case-study pages include screenshots of websites we built. The alt text describes what each one is, but fine detail inside those images isn’t transcribed.
• We don’t have a formal third-party audit. If accessibility is a compliance requirement for your organization, tell us and we’ll talk about what it would take.

What we won’t do

We won’t install an accessibility overlay widget — the floating button that promises to “make your site accessible” in one line of JavaScript. They don’t fix the underlying problems, they frequently interfere with the screen readers people already use, and they’ve drawn lawsuits rather than prevented them. We’d rather fix the markup.

Contacting the form

Our contact form asks for a name, an email address, and a message. Every field has a real label, nothing is placeholder-only, and there’s no CAPTCHA puzzle to solve. If the form is the thing that’s broken for you, email or call us directly — both work just as well, and we’d rather hear from you than not.

Tell us when something blocks you

If any part of this site is hard or impossible to use, we want to know. Please tell us the page you were on, what you were trying to do, and what device or assistive technology you were using if you know it — that’s usually enough for us to reproduce it.

• Email hello@cagii.com
• Call (727) 599-4913

We answer accessibility reports within two business days, and we’ll tell you honestly whether it’s a quick fix or a longer one. If something blocks you from information you need, we’ll get it to you another way while we fix the site.

A note on the sites we build

This statement covers cagii.com. The sites we build for clients are built to the same standard, but each one is its own project — if you’re a client and want to know where yours stands, ask and we’ll walk you through it.

Changes to this statement

As we close the gaps listed above, we’ll update this page and the date at the top will change with it. No silent edits.