Section 1
Who the EAA actually reaches
The EAA's scope is the first thing to get right, because both over-worrying and dismissing it are costly. The Act applies to economic operators, public or private, that provide covered products and services in the EU, which means a US business is potentially in scope if it sells to, or serves, customers in the European Union (1). A US consultancy with EU clients, a SaaS company with European users, an e-commerce operation shipping to Europe, these can fall within the Act's reach even with no EU office. The location of your servers or your headquarters is not the test; the location of your market is. The timeline matters. The key enforceable date was 28 June 2025, after which new services placed on the market must comply; all existing digital content must be fully compliant by 28 June 2030 (1). Enforcement runs through national authorities with complaint processes and surveillance monitoring, and non-compliance can carry penalties including fines (1). So a US business serving the EU is now operating against a live obligation with a hard final deadline. The EAA's test is not "where are you?" but "where are your customers?" A US business with European customers can be as bound by it as a business in Berlin, and "we didn't think it applied to us" is not a defense national regulators are obligated to accept.
Section 2
What it requires: WCAG 2.1 AA
The good news is that the technical standard is concrete and familiar. The EAA's requirements are operationalized through the harmonized European standard EN 301 549, which currently incorporates the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level (1). Conforming to WCAG 2.1 AA is the practical path to EAA compliance for a website, the same standard that underpins accessibility expectations in the US and globally. (WCAG 2.2 exists but is not yet incorporated into the harmonized standard, so 2.1 AA remains the operative benchmark (1).) This convergence is a gift: the work you do to satisfy the EAA is the same work that addresses US accessibility obligations and improves usability for everyone.
Section 3
Why even out-of-scope US businesses can't ignore accessibility
Here is the part that should reframe the topic even for the US business confident the EAA doesn't apply to it: the domestic accessibility-lawsuit environment is intense and increasingly aimed at smaller companies. In 2024, over 4,000 website accessibility lawsuits were filed in US state and federal courts (2). And the targets are not just giants, 67% of those cases were filed against companies with annual revenue under $25 million (2), with e-commerce the primary target and repeat suits common (41% of federal filings were against companies already sued once) (2). The image of accessibility litigation as something that happens only to corporations is simply false; small and mid-sized businesses are the majority of defendants. So the practical reality for a US service business is a pincer: the EAA creates a hard obligation if you serve the EU, and US ADA-based litigation creates real exposure regardless. Both point to the same response, actual WCAG 2.1 AA conformance, which means the question is no longer "does the EAA apply to me?" but "can I afford to keep operating an inaccessible website in this environment?" For most, the honest answer is no. (This pincer framing is my synthesis of the cited EU and US data.)
Section 4
The situation, in one view
The convergence in the bottom row is the strategic point: a single body of work, genuine WCAG 2.1 AA conformance, addresses the EU obligation, the US litigation risk, and (as the companion pieces in this library argue) a real conversion opportunity. Accessibility has shifted from an optional virtue to a baseline business requirement, driven simultaneously by European regulation and American litigation. The service businesses treating it as "not my problem" are the ones most exposed on both fronts.
Section 5
Execute This With AI
Here is a workflow to assess your exposure and plan a response with any capable AI model, paired with appropriate professional advice. Step 1, Inputs. Note whether you serve, sell to, or have users in the EU; your approximate revenue; your industry; and whether you've ever done any accessibility work. Step 2, Run the exposure-assessment prompt: You are an accessibility-compliance strategist (not a lawyer) helping a US service business understand its exposure under (a) the EU's European Accessibility Act, in force 28 June 2025, full compliance by 28 June 2030, standard WCAG 2.1 AA via EN 301 549, applies to businesses serving the EU market regardless of location, and (b) US ADA-based web litigation (4,000+ suits in 2024; 67% against companies under $25M revenue). My situation: EU customers/users? [yes/no/unsure]. Revenue band: [X]. Industry: [X]. Prior accessibility work: [none/some/describe]. Do five things: 1. Assess my likely EAA exposure and explain the reasoning (flag where I should confirm with an attorney). 2. Assess my likely US litigation exposure given my size and industry. 3. State the single standard I should target (WCAG 2.1 AA) and why it covers both. 4. Give me a prioritized first-90-days action plan toward conformance. 5. List what I should bring to a lawyer and an accessibility specialist. Be clear about what's informational vs. what needs professional/legal confirmation. Step 3, Reality check. "Based on my industry and size, how likely is a business like mine to face an accessibility complaint or lawsuit, and what's the cheapest meaningful step to reduce that risk this month?" Tools and expected output. Any frontier chat model for planning; a qualified attorney for legal determinations and an accessibility specialist for conformance. Expect an exposure assessment, the target standard, a 90-day plan, and a professional-consultation checklist. The QA discipline: treat the model's output as a planning aid, not a legal opinion, scope and liability determinations under the EAA and ADA are genuinely fact-specific and should be confirmed by a qualified attorney. The model helps you understand and prepare; the legal call is a lawyer's. The European Accessibility Act is not automatically "not your problem" just because you're American, its test is where your customers are, not where you are. And even if it genuinely doesn't apply to you, the US litigation environment, where the majority of accessibility suits now hit companies under $25 million, makes an inaccessible website a standing risk. The two pressures converge on one response, real WCAG 2.1 AA conformance, which happens to also be good for your users and your conversion. The businesses still filing accessibility under "later" are the ones a complaint or a deadline will eventually file it for them.
Section 6
Keep reading
Keep reading in the Accessibility & the EAA cluster and across the library: [The Business Case for Accessibility (Beyond Compliance)](/blog/the-business-case-for-accessibility-beyond-compliance), [Is Your Service Business Exposed to the European Accessibility Act?](/blog/is-your-service-business-exposed-to-the-european-accessibility-act), [Accessible Motion: Respecting Reduced-Motion Preferences](/blog/accessible-motion-respecting-reduced-motion-preferences). Also relevant: [The Motion Accessibility Mistake That Excludes Real Customers](/blog/the-motion-accessibility-mistake-that-excludes-real-customers), [The Service-Business Website Priority Stack: What to Fix First When Everything Needs Work](/blog/the-service-business-website-priority-stack-what-to-fix-first-when-everything-needs-work), [Why Service Businesses Lose Leads to Bad Websites](/blog/why-service-businesses-lose-leads-to-bad-websites).