Skip to content
←Back to blog

Does the EAA apply to B2B products or only consumer ones?

Does the EAA apply to B2B? Services: mostly no, it's built around consumers. Products: some yes, because payment terminals have no consumer test.

P

Pavel Charkasau

Does the EAA apply to B2B? For services, mostly not. For products, sometimes yes, and that second half is the part people miss. The European Accessibility Act covers services only when they are "provided to consumers" (Directive (EU) 2019/882, Art. 2(2)). A consumer is a natural person acting "for purposes which are outside his trade, business, craft or profession" (Art. 3(22)). A service sold only to companies and used only by their staff usually falls outside the service duties. The product list in Article 2(1) works differently. Payment terminals, ATMs, ticketing machines, check-in machines and interactive information terminals carry no consumer test at all. A card terminal you sell to a shop is a B2B sale of an in-scope product. Computers, smartphones and e-readers are framed around the consumer, but by what the product is, not who paid for it. So the honest answer depends on two things: whether you sell a product or a service, and whether a consumer ever reaches the interface. Below I go through both halves clause by clause. It's my reading of the text, not legal advice.

Does the EAA apply to B2B services?

Generally no, if the service is truly business-only. The chapeau of Article 2(2) says the directive "applies to the following services provided to consumers after 28 June 2025" and then lists them: electronic communications, access to audiovisual media, certain passenger transport elements, consumer banking, e-books and dedicated software, and e-commerce (Art. 2(2)).

The consumer qualifier also turns up inside the definitions, which closes the obvious loopholes. E-commerce services are defined as services provided at a distance "at the individual request of a consumer with a view to concluding a consumer contract" (Art. 3(30)). Consumer banking services means "the provision to consumers" of the listed financial services, such as credit agreements and payment services (Art. 3(28)). A procurement portal where registered companies order stock on account terms doesn't conclude consumer contracts. A corporate treasury platform isn't consumer banking.

Two details in Article 3(22) matter for edge cases:

  • The consumer is a natural person. A company is never a consumer under this definition.
  • The test is the purpose of the purchase. A freelancer buying a laptop for client work is acting within their trade. The same person buying a train ticket for a holiday is a consumer.

Electronic communications have one extra carve-out. Article 2(2)(a) excludes "transmission services used for the provision of machine-to-machine services". So an IoT connectivity contract between a carrier and a fleet operator is out on two counts: there is no consumer, and the M2M exclusion applies anyway.

Does the EAA apply to B2B products?

Yes, for some of them. Article 2(1) lists the covered products, and the wording is not uniform:

Product (Art. 2(1))Consumer qualifier in the text?What that means for a B2B sale
(a) Consumer general purpose computer hardware and their operating systemsYes, through the definition in Art. 3(39)Judged by the type of product, not the buyer
(b)(i) Payment terminalsNoIn scope when sold to merchants
(b)(ii) ATMs, ticketing, check-in and interactive information terminals for covered servicesNoIn scope when sold to banks, operators, venues
(c) Consumer terminal equipment for electronic communicationsYes, "consumer" in the itemJudged by the type of product
(d) Consumer terminal equipment for audiovisual mediaYes, "consumer" in the itemJudged by the type of product
(e) E-readersNo qualifierCovered as a category

Row (b) is the clearest B2B case in the directive. Nobody buys a payment terminal for personal use. Manufacturers sell them to retailers, payment service providers and acquirers. Recital 26 says the directive "should also cover payment terminals, including both their hardware and software" (recitals). The people who need the terminal to be accessible are the shoppers at the till, not the business that bought it. The obligation sits with the manufacturer, importer and distributor of the terminal, all of which are B2B roles here.

The self-service list in (b)(ii) works the same way, with one limit. The terminals must be "dedicated to the provision of services covered by this Directive", so a ticket machine for rail travel is covered, but a factory-floor kiosk for logging shifts is not. Terminals installed as integrated parts of vehicles, aircraft, ships or rolling stock are excluded. We went through kiosk requirements in the EAA and self-service terminals.

Is a laptop sold to a company still a consumer product?

Usually, yes. This is my reading, so weigh it accordingly. Article 3(39) defines a consumer general purpose computer hardware system by its nature: a complete computer, "characterised by its multipurpose nature", able to perform "most common computing tasks requested by consumers and intended to be operated by consumers", naming desktops, notebooks, smartphones and tablets.

Nothing in that definition asks who bought the unit. A notebook model sold through a business channel is the same notebook. It is still a multipurpose computer intended to be operated by people. I would not plan on an exemption just because the invoice goes to a company. Where the definition does bite is specialised equipment. Recital 25 says "specialised computers embedded in consumer electronics products" are not general purpose systems, and single components such as "a mainboard or a memory chip" are not covered on their own (recital 25). A ruggedised handheld built only for warehouse scanning is a reasonable candidate for falling outside, but that's a product-by-product call for your counsel.

What about B2B2C: software your customers put in front of consumers?

Here the B2B label stops helping. Say you sell a booking engine to hotels, or a checkout component to retailers. Your contract is with a business. But the screens you render are where the hotel's guests and the shop's customers conclude consumer contracts. Your customer is the service provider under Article 13, and it has to "design and provide services in accordance with the accessibility requirements" (Art. 13). It can't do that if your widget traps keyboard focus.

Recital 20 says that when "a service, or part of a service, is subcontracted to a third party, the accessibility of that service should not be compromised". In practice the duty reaches you through the contract, an accessibility clause or a request for an EN 301 549 conformance report, even though the directive names your customer. We covered the SaaS version in more detail in EAA compliance for SaaS and B2B software.

My opinion, stated plainly: "we're B2B" is the most common scope mistake I see, and it's rarely a lie. The sales motion is B2B, but the pixels are B2C. Sort your product by who can reach each screen, not by who signs the order form.

Which B2B cases are genuinely out of scope?

Some really are. Based on the text, these usually sit outside the directive:

  • An internal HR, payroll or ERP system used only by employees.
  • A wholesale ordering portal limited to registered trade accounts.
  • B2B payment rails and corporate banking that never serve a natural person acting privately.
  • Machine-to-machine connectivity (Art. 2(2)(a)).
  • Industrial equipment that isn't on the Article 2(1) list.

Out of scope for the EAA doesn't mean out of scope for everything. Public sector websites and apps fall under the Web Accessibility Directive, Directive (EU) 2016/2102, and EU employment equality law requires reasonable accommodation for disabled workers (Directive 2000/78/EC, Art. 5). An inaccessible internal tool can become the employer's problem, and then a procurement requirement for the vendor. The EAA is also a directive, so each member state transposes it into its own law. Check the national text for the markets you sell into.

How do you check where your product sits?

Ask three questions, in order:

  1. Product or service? If you place hardware on the market, check it against the Article 2(1) list first. If it's a payment or self-service terminal, the buyer being a business doesn't take it out.
  2. Can a consumer reach it? For services, list every surface: marketing site, pricing, sign-up, checkout, help centre, emails, embedded widgets. Any surface where a natural person acting privately can request a covered service or conclude a contract is a candidate.
  3. Are you a microenterprise? Article 4(5) exempts microenterprises "providing services", meaning fewer than 10 persons and turnover or balance sheet not exceeding EUR 2 million (Art. 3(23)). It doesn't cover products. See the microenterprise exemption, explained.

For the surfaces that land in scope, the practical standard is EN 301 549, whose web clauses map to WCAG 2.1 AA. Start with an automated pass: our free scan runs axe-core in a real browser and gives you the failing selector, such as a button.checkout-submit with no accessible name. Then do the part a scanner can't. Deque's analysis of more than 2,000 audits found automated testing caught about 57% of issues by volume, and roughly 30% counted by WCAG success criteria (Deque). The rest needs a person with a keyboard and a screen reader. Our WCAG checklist lists the manual checks, and the accessibility statement guide covers what you publish once you know where you stand.

Frequently asked questions

Does the European Accessibility Act apply to B2B companies?

It depends on what they sell. Services fall under the EAA only when provided to consumers, so purely business-only services are generally outside it, but products like payment terminals and ATMs are covered even when sold to businesses.

Are payment terminals covered by the EAA if we only sell to merchants?

Yes. Article 2(1)(b)(i) lists payment terminals with no consumer qualifier, and recital 26 says both hardware and software are covered, so the manufacturer, importer and distributor carry the product obligations regardless of the buyer.

Is a company buying a service a "consumer" under the EAA?

No. Article 3(22) defines a consumer as a natural person acting for purposes outside their trade, business, craft or profession, so a company is never a consumer and neither is a freelancer buying for their work.

Does the EAA cover B2B software that our customers show to consumers?

Indirectly, yes. Your customer is the service provider and must make its service accessible, including subcontracted parts (recital 20), so the requirement usually reaches you through the contract.

Is our internal employee tool covered by the EAA?

Usually not, because no consumer uses it. Other laws can still apply, such as EU employment equality rules on reasonable accommodation and the Web Accessibility Directive for public sector bodies.

Map your surfaces first

List the screens a consumer can reach, then run a free scan on each one. You'll know quickly whether your "B2B" product has a consumer edge, and what's broken on it.


Pavel Charkasau, founder, wcagc.com. Last updated 16 November 2026.

Sources