WCAG 2.1 AA. Across every page.

Target conformance

This site is built to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. The same bar is the floor on every client engagement we ship — not the ceiling. Where AAA conformance applies cleanly without compromising design or editorial intent (color contrast, focus visibility, motion preferences), we honor it.

Site practices

The specific accessibility patterns this site implements:

• Semantic HTML. Landmark regions (header, nav, main, footer) on every page; heading hierarchy enforced (a single h1, then h2 sections, no skipped levels); lists, figures, and forms use their proper elements rather than styled divs.
• Keyboard navigation. Every interactive element is reachable via Tab; focus order matches visual order; the skip-link at the top of every page jumps straight to #main for screen-reader users.
• Visible focus indicators. Two-pixel cyan outlines on every focusable element, with offset so the indicator never gets clipped by surrounding chrome.
• Color contrast. Every text + background combination on the site clears WCAG 2.1 AA contrast ratios (4.5:1 for body text, 3:1 for large text and non-text UI elements).
• Motion preferences. Every animation honors the prefers-reduced-motion: reduce media query — aurora glows, hover lifts, and CTA gap-widening all freeze when the OS-level reduced-motion preference is set.
• Alt text on every meaningful image. Decorative images use alt="" + aria-hidden="true"; informative images (case-study heroes, client logos, gallery shots) carry descriptive alt text.
• Forms. Every form input has a programmatically associated label, error messages are tied to fields via aria-describedby, and the contact form’s submit state is announced via an ARIA live region.

Testing approach

Three layers of accessibility testing run against every page on this site:

• Automated. axe-core and Lighthouse’s accessibility audit run pre-deploy. Both catch the broad class of programmatic issues (missing labels, contrast failures, ARIA misuse, focus-trap leaks).
• Manual keyboard. Every page is walked Tab-by-Tab to confirm focus order, focus visibility, and that every interactive element can be actuated without a mouse.
• Manual screen-reader spot-checks. VoiceOver on macOS and NVDA on Windows are used to spot-check the home page, case-study detail pages, the contact form, and the 404 page. Screen-reader testing catches what automated tools cannot — landmark coherence, heading flow, and whether the narrative actually reads correctly out loud.

Known issues

No known WCAG 2.1 AA conformance failures at the time of last review. If you encounter one, the next section is how to tell us.

Accommodation requests

If any part of this site doesn’t work for you — a control isn’t reachable, a contrast ratio looks wrong, an animation is causing trouble, a screen-reader announcement doesn’t match the visual content — email us. We’ll respond within twenty-four hours, every weekday, and we’ll fix the underlying issue rather than ship you a workaround.

The same email address handles accessibility-related questions about any engagement INNOV8 has shipped or is in talks about — not just about this site. Accessibility is in scope on every engagement; this page exists so you don’t have to take that on faith.