From Reactive Widgets to Proactive Code: How OluKai Achieved WCAG 2.2 AA Compliance Across a Multi-Brand Portfolio

The Scenario: A Global Footwear Leader with a Growing Compliance Challenge

‍OluKai, founded to create premium footwear that honors Hawaiian culture, integrates native island-inspired stories into its design and community investment. Sold across major retailers and direct-to-consumer via Shopify, OluKai serves customers across the US, Canada, and Europe — operating multiple storefronts as part of a larger portfolio of brands managed by Tradewind Services.

Despite OluKai's strong brand values and customer-first ethos, digital accessibility had become a persistent — and reactive — challenge. The team was doing their best: sprinkling accessibility tasks into engineering sprints every few weeks, and relying on a JavaScript overlay widget as their primary compliance tool. But as the site grew more complex, the gaps kept widening.

The deeper issue wasn't effort — it was the tool. Accessibility widgets like AccessiBe and EqualWeb promise a shortcut: inject a JavaScript overlay, claim compliance, move on. But in practice, overlays cannot fix what lives in the source code. WCAG criteria around alt text, ARIA attributes, keyboard navigation, color contrast, and heading structure require actual code remediation — not a band-aid layered on top.

When OluKai's engineering team began to question whether the widget approach was truly keeping them protected — especially given growing legal pressure across the e-commerce industry — they started looking for something fundamentally different.

The Solution: Code-First Compliance for a Complex Shopify Ecosystem

OluKai came to TestParty looking for experts, not just a tool. With multiple brands sharing a global Shopify codebase, any accessibility solution would need to understand the nuances of their repo, work within their existing development workflow, and scale across a portfolio — not just fix one site in isolation.

TestParty's engagement with OluKai began in January 2026 with a structured, phased approach:

1. Baseline Scan and Audit: TestParty ran a comprehensive site-wide accessibility scan to identify all WCAG violations — from missing alt text and broken ARIA attributes to target size failures and empty heading elements.
2. Code-Level Remediation PR: Within two weeks, TestParty delivered a pull request with 121,700 code changes — fixing structural issues across product pages, collection templates, navigation, and filterable content systems. Changes were made directly in OluKai's GitHub repo, following their existing PR review process.
3. Third-Party Integration Audit: Four embedded third-party tools were flagged for accessibility issues. TestParty categorized each: Stockist and Gorgeous were identified as low-severity and non-critical; Spotify and Reviews IO required direct vendor engagement, and OluKai was supported in crafting outreach communications to those teams.
4. Accessibility Statement and Accepted Exceptions: For brand colors that OluKai chose not to change (certain neon collection page colors that could not meet contrast ratios without compromising brand identity), TestParty drafted a formal accessibility statement documenting those known exceptions — the right legal approach when color choices are intentional.
5. Transition to Continuous Monitoring: After initial remediation, TestParty shifted OluKai to an ongoing maintenance cadence: automated scans run weekly, with a monthly PR delivered for any new or regressed issues. The first maintenance PR contained just ~20 lines of changes — a testament to how dramatically proactive remediation reduces ongoing work.

One of the key differentiators for OluKai's team was TestParty's ability to get up to speed on their codebase without hand-holding. Justyne noted that TestParty was 'able to understand our repo very easily and able to deliver everything on time' — critical for a team where engineering capacity is always stretched thin.

The Results: Permanent Compliance Without the Engineering Tax

Within two months of engaging TestParty, OluKai had achieved the following:

• WCAG 2.2 AA Compliance: Core site is compliant with the current accessibility standard, with clearly documented exceptions for intentional brand color choices.
• A Defensible Legal Record: Weekly scan reports and monthly PR logs create a continuous paper trail — exactly what a legal team needs to demonstrate good-faith compliance efforts in the event of any ADA challenge.
• Zero Disruption to Engineering Workflows: All changes were delivered via pull requests to OluKai's existing GitHub repo, reviewed by their own developers, and merged on their timeline — no black-box overlays, no mysterious JavaScript.
• Multi-Brand Portfolio Coverage: Global code changes propagated across OluKai's US, Canadian, and European storefronts from a single implementation, and laid the groundwork for extending the same approach to Melin, Roark, and other portfolio brands.
• A New Model for Accessibility Prioritization: Instead of competing with product roadmap tickets, accessibility is now handled as a parallel, automated process — freeing OluKai's engineers to focus on feature work.

Beyond OluKai: A Portfolio-Wide Strategy

The success of OluKai's implementation has opened a broader conversation within Tradewind Services. With a shared Shopify codebase across multiple brands, the efficiencies of TestParty's approach become even more compelling at scale: fixes made to global snippets and section templates propagate across the entire portfolio, meaning each additional brand added to the program requires significantly less initial remediation work than the first.

Tradewind's team is now actively planning to expand TestParty's engagement to their full brand portfolio — bringing the same weekly scan, monthly PR, and continuous compliance model to every storefront they manage.

As Michael Bervell, CEO of TestParty, framed it on their final check-in call: "There's getting compliance, and there's proving compliance. The proving compliance is how your legal team will feel comfortable saying, 'We know that we're accessible — here's all the evidence.' That's the goal."

Sound Familiar?

OluKai's journey — from reactive widget dependency to proactive code-level compliance — is one we see across the e-commerce industry. If your team is spending engineering cycles on accessibility backlog, relying on overlays that aren't truly fixing your code, or simply unsure whether your site would hold up in a legal review, TestParty can help.

Visit testparty.ai to book a demo and see what a real accessibility audit of your Shopify store looks like.