From AudioEye Audits to Fixed Code: How Lime Crime Made Its Shopify Store Accessible With a Lean Team

THE SCENARIO

Lime Crime does not do subtle. The storefront at limecrime.com opens on “Never Blend In,” and the promise underneath reads “We create kick-ass products so you can create looks as unique as you.” The manifesto is louder still: “Time to wipe away the blandness in beauty. The world needs more color, more fun, more character, more creativity.”

The line that matters most here is the one about invitation. “Our hair and makeup invite self-expression - celebrating what makes us truly unique.” Lime Crime is built on letting people in, and says so again in its animal-welfare commitments: “Everyone at our company is committed to creating animal-friendly products for everyone.” Four trust pillars sit on the home page, 100% Vegan, Cruelty-Free, Kind to the Planet and Conscious Beauty, with PETA certification and Leaping Bunny verification behind them. Elsewhere the manifesto shrugs that “rules need not apply.” Web accessibility rules are the exception, and they apply whether or not a brand still has a developer.

The catalogue is tight and the storefront is busy: Unicorn Hair Full Coverage and Tints in two sizes, bleach kits, a Color Prep Kit, gift cards and a sale collection, wrapped in a currency selector, accounts and cart, an announcement bar, newsletter capture, a reviews page, FAQ and color instruction pages, order tracking, and third parties including a Gorgias support chat, hCaptcha and Afterpay.

Then there is the navigation choice that makes this a pointed accessibility problem. Lime Crime’s primary browsing axis is Shop By Color: blue, green, neon, orange, pastel, pink, purple, red. For a hair-dye brand that is the obvious merchandising decision. It also means color is doing the work of a label, exactly the territory WCAG’s use-of-color and contrast criteria govern. A brand whose identity is color has more accessibility to get right, not less.

---

THE CHALLENGE

Lime Crime had not ignored accessibility. It had paid for it twice. Allyant came first, then AudioEye, still in place when TestParty spoke to the team in January 2026. What AudioEye supplied, in their description, was “just the basic sort of compliance” plus a site audit roughly every quarter. What it did not supply was anyone to carry that audit out.

This is the structural flaw in the audit-report model, and one of the most common patterns in ecommerce website accessibility. An accessibility audit report describes a problem but is priced as though it were the solution, because it assumes an implementation team on the other side. While Lime Crime still had developers, they sat on an hourly retainer and each quarterly audit consumed two to four of those hours, neither free nor spare.

Then the developers went, and the audits kept coming. “We no longer have any developers,” a representative said in January, describing a gap that had already run about a year. The ecommerce team that had absorbed some of the work went too. They were left holding a project without the specialist knowledge to grade it: the audits would “compound the time,” they explained, “because then we’re scrambling, trying to learn.” When questions came up mid-remediation, “it was hard to figure that part out.”

Two vendors, a shelf of audit reports, and no mechanism to turn either into a fixed line of code.

---

THE SOLUTION

They found TestParty by searching for it. Assembling a shortlist of about four vendors, they read their way to a conclusion: “It kind of seemed like you guys were more involved, a more comprehensive” option. The brief she was buying against was unusually clear, and unusually modest.

That brief rules out most of the category: overlays need someone to trust them, audits need someone to action them. TestParty took the whole job rather than the reporting half, the working distinction between tools that fix and tools that only report. With no developers and no GitHub workflow left, the engagement ran entirely inside Shopify: TestParty joined the store with a partner access code, duplicated the live theme, and remediated the source code inside that duplicate across a two-week window. The ecommerce team’s only job at the end was to review it and merge.

Kickoff was Feb 9, 2026, and onboarding took about ten minutes of a scheduled thirty. The work then settled into weekly automated scans, a monthly manual audit, and a monthly remediation report dated the 13th, with biweekly calls alongside TestParty’s CTO for the first two months to walk the code changes before they went live.

One deliverable is worth isolating, because it is the part a customer can point at. On Mar 9, 2026 TestParty drafted an accessibility statement, Lime Crime reviewed it in Shopify on the call, and it went live in the footer the same day, with a phone number and a reporting form so anyone who hits a barrier reaches a human.

---

THE RESULTS

Lime Crime came in asking for reassurance rather than a number, and reassurance is what it can speak to eight weeks in. The test was whether a team with no developers and no accessibility specialist could stop worrying about the problem.

The more concrete result is a headcount question answered in the negative. Asked at week eight whether Lime Crime still needed developers for accessibility, the team’s answer was that the requirement had moved rather than shrunk. The work still happens; it just does not happen at Lime Crime. That is the shape of Ollie replacing four years of audit reports with 451 fixes in two weeks, and of right-sizing accessibility as a lean team.

Two outcomes are visible from outside. The first is the published statement, the only fully verifiable deliverable here. The second is the shape of the engagement: at week eight the biweekly check-ins were retired by mutual agreement, because nothing was left to review that a monthly report could not carry. Vendor relationships that get quieter rather than louder are the ones that worked, the pattern behind Case-Mate finally finding a long-term accessibility partner.

---

THE ROAD AHEAD

Lime Crime is in maintenance mode, which is where it wanted to be. Weekly scans continue, the monthly audit and report land on the 13th in both email and the portal, and Lime Crime has put that cadence on the calendar so her manager can see it. Dedicated calls have given way to an open email thread and ad hoc reviews whenever something substantial ships. “I don’t think we’re rolling out anything,” they said at week eight. “So it should just be the ongoing maintenance.”

That plan holds as long as the site holds still, and it will not forever. The March spring sale was handled the right way, a direct duplicate of the remediated theme with only the banner swapped, so the accessibility work survived the campaign. That habit is the thing to protect: a remediated theme stays accessible only until someone forgets which theme they duplicated. Third-party components are the other open surface, particularly the support chat, and the frontier past conformance is whether a Shopify store is legible to AI shopping agents at all, which turns on the same semantic markup.

For a brand whose home page reads “Never Blend In,” the point was never to quietly clear a checklist. It was to keep the invitation open to everyone who wanted to make their own mark.

Ready for your accessibility upgrade?

Book a demo today: https://testparty.ai/book-a-demo