Episode 08 — Selling globally without getting burned

HOST A:  Last episode was almost entirely about the EAA. Today I want to widen the lens, because the EU is not the only jurisdiction retailers need to be thinking about, and I think treating this as a single-country problem is exactly the mistake that gets companies burned.

HOST B:  Let’s start with the U.K., since the report specifically calls it out as a separate, parallel track from the EAA.

HOST A:  Right, and this is an important distinction, because the U.K. is no longer part of the EU, so EAA enforcement doesn’t automatically apply there. But that doesn’t mean the U.K. is some kind of accessibility safe harbor. In the U.K., enforcement is happening under the Equality Act 2010 and the Public Sector Bodies Accessibility Regulations.

HOST B:  Two different pieces of legislation, separate from EAA entirely.

HOST A:  Completely separate legal frameworks, with their own enforcement mechanisms. And critically, the report notes that regulators in the U.K. are signaling increased scrutiny of eCommerce sites specifically.

HOST B:  So it’s not a static, long-standing law that’s just sitting there unenforced. It’s an area where enforcement attention is actively increasing right now.

HOST A:  Which means a retailer who’s spent the last several months focused entirely on EAA readiness, because that’s the headline regulation everyone’s been talking about, could be missing a second, distinct compliance obligation in the U.K. market that’s heating up in parallel.

HOST B:  This is exactly the trap I want to dig into for this episode — the idea that “we did our EU compliance work” can create a false sense of complete coverage.

HOST A:  That’s precisely the risk, and I think the report’s phrase captures it well: for international retailers, accessibility is truly a global mandate. Not a single-jurisdiction checkbox you complete once.

HOST B:  Let’s zoom out even further, beyond just the EU and the U.K., because I think this pattern — multiple, independent regulatory frameworks all converging on similar accessibility requirements — is becoming the norm globally, not the exception.

HOST A:  It really is becoming the standard pattern, even though we’re focusing today specifically on what the report covers, which is the EU and U.K. landscape. The broader strategic point is this: as more countries and regions introduce their own digital accessibility regulations — each potentially with their own specific legal language, their own enforcement bodies, their own penalty structures — a retailer selling into multiple markets is going to face an increasingly fragmented compliance landscape if they try to handle each one as a completely separate, bespoke project.

HOST B:  Which is presumably both expensive and operationally fragile — you’d need a different compliance workstream for every region you sell into.

HOST A:  Exactly, and that’s actually the most useful insight from this episode, in my opinion. The way out of that fragmentation isn’t tracking every individual country’s specific legal text. It’s anchoring to the technical standard that keeps showing up underneath nearly all of them.

HOST B:  WCAG 2.1 AA again.

HOST A:  Again. We’ve now referenced it in the context of U.S. litigation in episode two, in the context of the EAA last episode, and now in the context of U.K. enforcement under the Equality Act and Public Sector Bodies Accessibility Regulations. Three completely separate legal regimes, three different enforcement bodies, three different penalty structures — and the underlying technical bar that regulators and courts keep referencing across all of them is substantially the same.

HOST B:  So practically, if a global retailer builds their digital experience to genuinely meet WCAG 2.1 AA, they’re not building three separate compliance programs. They’re building one technical foundation that happens to satisfy multiple legal frameworks simultaneously.

HOST A:  That’s the strategic unlock here, and I think it’s worth saying plainly because it cuts against how a lot of legal and compliance teams instinctively approach multi-jurisdiction risk — which is often to build separate playbooks per region. Accessibility doesn’t really work that way, because the underlying technical reality of “can a screen reader user complete this checkout flow” doesn’t change based on which country that user happens to be shopping from.

HOST B:  Let’s talk about what actually goes wrong when companies don’t take this unified approach, because I think “getting burned” in the episode title implies some specific, avoidable failure modes.

HOST A:  A few patterns show up repeatedly. One: companies localize their content and currency for a new market, but never actually re-test the accessibility of that localized experience — assuming that because the English version passed an audit, the French or German version is automatically fine too, when in practice translated content can introduce entirely new accessibility issues, like text that no longer fits properly in a UI element, or alt text that didn’t get translated at all.

HOST B:  That’s a subtle one — accessibility work that doesn’t travel automatically with localization.

HOST A:  Exactly. Second pattern: companies treat EAA readiness as the finish line, then get caught off guard by a completely separate U.K. enforcement action, exactly the trap we described earlier in this episode. Third: companies build accessibility fixes reactively, market by market, in response to specific legal threats, which results in inconsistent quality and coverage across their global footprint — fully fixed in one market, barely addressed in another.

HOST B:  Which sounds expensive and chaotic compared to just building one strong technical foundation from the start.

HOST A:  That’s really the core argument for this episode. Reactive, market-by-market compliance is slower, more expensive in aggregate, and riskier than building toward a single, robust accessibility standard that happens to satisfy multiple jurisdictions at once.

HOST B:  Let’s bring this back to something practical. If a retailer is selling into, say, the U.S., the EU, and the U.K. simultaneously — which is an extremely common footprint — what does a sane, unified strategy actually look like?

HOST A:  I’d frame it in four parts. First, adopt WCAG 2.1 AA as your single internal technical standard, regardless of which specific market you’re building for — make it the default bar for every product, every page, every market, not a market-specific add-on. Second, build accessibility testing into your localization process specifically, so translated and region-specific versions of your site get the same scrutiny as your primary market version, closing that localization gap we just discussed. Third, maintain a single, centralized accessibility audit and remediation log that covers your entire global footprint, so you have one source of truth instead of fragmented, region-specific documentation. And fourth, stay aware of the regulatory specifics in each individual market you sell into — EAA penalty structures, U.K. enforcement bodies, U.S. litigation patterns — not because you need a separate technical approach for each, but because you need to understand what’s actually at stake in each jurisdiction if you fall short.

HOST B:  So one technical foundation, with market-specific legal awareness layered on top, rather than market-specific technical approaches built from scratch each time.

HOST A:  That’s exactly the model. And I think it’s worth connecting this back to something from episode one — the idea that accessibility functions as infrastructure. Infrastructure, by definition, is something you build once and that supports many different things on top of it. Multi-jurisdiction compliance is a perfect example of that principle in action. You don’t rebuild your payment processing infrastructure separately for every country you sell into — you build a robust core system and adapt the specifics around it. Accessibility works the same way.

HOST B:  Let’s close with the framing for this episode. “Selling globally without getting burned” — what’s the one-sentence version of how a retailer actually does that?

HOST A:  Build to a single, rigorous accessibility standard as your technical foundation, understand the specific legal landscape in every market you operate in, and never assume that compliance in one jurisdiction automatically covers you in another.

HOST B:  That feels like a genuinely actionable takeaway, not just a warning.

HOST A:  Which sets up our next episode nicely, because we’re shifting away from legal and regulatory risk for a bit, and into something more focused on growth and customer experience — hyper-personalization, and why the report argues that truly personal experiences have to be accessible ones, or they’re not actually personal at all.

HOST B:  Looking forward to that one. See you there.

HOST A:  Thanks for listening.