Corridor Web Co.
Accessibility

We try to build websites everyone can actually use.

Accessibility isn't a checkbox we get to ignore because we're a small shop. Here's what we aim for, what we know isn't perfect, and how to tell us when we get it wrong.

Last updated: May 1, 2026

What we aim for

We design and build this site (and the sites we build for clients) toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We're not perfect, but that's the standard we're working toward on every page.

What that looks like in practice

  • Keyboard navigation. Every interactive element on the site (links, buttons, form fields, the theme toggle, etc.) is reachable with the Tab key and operable without a mouse.
  • Visible focus. Whatever element is currently focused gets a visible outline so keyboard users can see where they are.
  • Sufficient color contrast. Body text and interactive elements meet the WCAG AA contrast ratio (4.5:1 for normal text). Our dark mode is engineered to maintain the same standard.
  • Semantic HTML. We use real headings, real buttons, real form labels, and real lists — not divs that pretend to be other things.
  • Image alt text. Meaningful images have descriptive alt text. Decorative-only images are marked as hidden from assistive technology.
  • Responsive layout. The site reflows cleanly from a 320px-wide phone all the way up to a desktop monitor without losing functionality.
  • Reduced-motion respect. We avoid auto-playing motion that can't be stopped. Animations are subtle and skippable.

Things we know aren't perfect

Honesty matters more than a polished statement. A few areas we're still actively improving:

  • Demo sites under /demos/*. The demos are concept designs meant to demonstrate aesthetic range. They meet most WCAG AA criteria but aren't held to the same QA bar as the real site, since they're illustrative rather than transactional.
  • Some live previews and iframes. Embedded previews in the client editor may not perfectly inherit parent-page focus management. We're iterating on this.
  • Third-party tools. Stripe's checkout page, Resend's links, and similar embedded flows are outside our direct control. Those vendors maintain their own accessibility statements.

How to report a problem

If something on this site doesn't work for you, we want to know. Please tell us:

  • What page (URL) the issue is on.
  • What you were trying to do.
  • What assistive technology you're using (screen reader, voice control, magnifier, etc.) — if applicable.
  • What happened that you didn't expect.

Send it to us:

We aim to respond within 2 business days and will work with you on a workaround while we fix the underlying issue. We'll never charge you for reporting an accessibility issue and we'll never make you sign anything before we help you.

Accessibility in the sites we build for clients

The same standards apply to the websites we build for our clients. Every site we ship is reviewed for keyboard navigation, contrast, semantic markup, and alt text before launch. If you're a Care + SEO or Lead Engine subscriber and you discover an accessibility regression, it falls under your "quick edits" coverage at no extra charge.

Formal complaints

If we don't resolve your accessibility concern to your satisfaction, you have the right to file a complaint with the U.S. Department of Justice under the Americans with Disabilities Act. We'd rather just fix it for you, but you have that option.

Contact

MarathonMeta LLC
d/b/a Corridor Web Co.
Coralville, IA
hello@corridorwebco.com · (319) 328-8022

Text (319) 328-8022Free mockup