Skip to content
Pandus

Is accessibility required for B2B and company websites?

Usually not by the European Accessibility Act, which covers services for consumers. A B2B or company website is reached by other routes: public tenders that require EN 301 549, US buyers that ask for a VPAT, the ADA for businesses open to the public and the UK Equality Act for services. Here is what applies to whom.

By , founder of Pandus · Updated October 21, 2026 · 5 min read · How we write and check our guides

The question arrives in two forms. A German marketing manager asks whether the BFSG makes the company website “pflicht”. A SaaS founder gets a procurement questionnaire with the line “attach your Accessibility Conformance Report”. The honest answer has several parts, because no single law covers “websites”. The laws cover services, buyers and sellers, and a B2B site sits between them.

What the European Accessibility Act does and does not cover

Directive (EU) 2019/882, the European Accessibility Act, applies since 28 June 2025 to a list of products and to services for consumers: e-commerce, consumer banking, electronic communications, access to audiovisual media, passenger transport and e-books. National laws transpose it: the BFSG in Germany, the Polish act on ensuring accessibility requirements, and so on.

Two consequences for a B2B site:

  • A website that sells goods or services only to companies is not an e-commerce service for consumers in the sense of the directive. The EAA does not reach it.
  • A company website that merely presents the company, with no consumer service on it, is not covered either. Information pages are not in the list.

The border is the service, not the domain. A manufacturer with a B2B portal and a small consumer shop under the same brand has a covered part (the shop) and an uncovered part (the portal). A SaaS with a plan for private users offers a consumer service. When in doubt, the EAA filter walks through the three questions, and the EAA guide has the country details.

Public bodies and the people who build for them

Public-sector websites and apps in the EU fall under Directive (EU) 2016/2102, the Web Accessibility Directive, with EN 301 549 as the technical standard and a mandatory accessibility statement. That duty is the public body’s. It reaches private companies in two ways:

  1. You build the site. An agency or a contractor delivering a municipal portal, a school site or a ministry service delivers against EN 301 549, and the acceptance test checks it. In Ukraine the same standard is adopted as ДСТУ EN 301 549:2022.
  2. You sell software to the public sector. EU public procurement rules (Directive 2014/24/EU, Article 42) say that technical specifications shall take into account accessibility criteria for persons with disabilities, except in duly justified cases. In practice tenders list EN 301 549 and ask for evidence. In the US, Section 508 does the same for federal purchases, and the evidence is an Accessibility Conformance Report in VPAT format.

For a B2B software company this is the most common route by which accessibility becomes a requirement: not a law aimed at you, but a buyer who cannot sign without it.

The United States and the United Kingdom

In the US, Title III of the ADA covers places of public accommodation, and courts have applied it to the websites of businesses that serve the public, such as shops, hotels and restaurants. The Department of Justice has said that it reads the ADA as covering web accessibility for such businesses. Whether a site that serves only other businesses falls under it is argued case by case, and demand letters do not always wait for the answer. Our page on ADA website compliance explains the wording we use and avoid; it is not a legal opinion.

In the UK, the Equality Act 2010 places a duty on service providers not to discriminate and to make reasonable adjustments. The law does not distinguish by website type, so a company offering services through its site has the duty whoever the customer is. The public-sector regulations add stricter rules for public bodies; see UK accessibility regulations.

When nothing applies directly

Many B2B and company websites end up in this group: no consumer service, no public-sector contract, outside the US and the UK. Three reasons still put accessibility on the list.

  • Your buyers ask. Enterprise security and vendor questionnaires increasingly include an accessibility section. A clear answer with a date, a standard and a list of known limitations beats an empty field.
  • Your visitors include everyone. A procurement manager with low vision, a developer who uses only the keyboard, a decision-maker reading your pricing on a phone in the sun: the same WCAG criteria decide whether they get through the form.
  • It is cheap to know. An automated check against WCAG 2.2 AA takes a minute per page and finds the most common problems: contrast, labels, unnamed buttons, images without text. It does not find everything, and we say so on every report.

A practical order of work

  1. Decide which group you are in. Consumer service, public-sector supplier, or neither. Write it down; it tells you which standard a buyer will quote.
  2. Check the pages that matter for business: the home page, pricing, the sign-up or demo form, the sign-in page. The free check covers one page; the browser extension checks pages behind the login.
  3. Fix the blockers first: anything that stops a keyboard or screen reader user from signing up or signing in. The WCAG 2.2 checklist lists them in plain words.
  4. Publish an accessibility page. Even where it is not mandatory, a short page with what was checked, what is fixed and how to report a barrier answers most questionnaires. The accessibility statement guide has a template.
  5. Keep it checked. Releases and CMS updates bring problems back. A weekly check with “new since last check” catches them before a buyer does. For web applications, the testing guide covers the states a crawler cannot reach.

Pandus does the automated part: weekly checks of every page, live barriers behind the login with the SDK, reports in seven languages and, on Agency plans, a draft ACR in VPAT format marked as a draft. It is an automated check, not a full audit, and nothing on this page is legal advice.

Guides and tools

Help articles