← PitchGap

EAA website check: scope before the scan

A manual scope and evidence guide for agencies. Published 5 November 2026. Sources reviewed 5 November 2026.

An EAA website check starts with the service your client provides, not a scanner score. The European Accessibility Act covers specified products and consumer services. A website is not covered simply because it exists.

Run a free audit for initial website signals. PitchGap does not decide EAA applicability or certify accessibility. Its findings need human verification.

First record the service, operator, country and consumer journey. Then test barriers people encounter. Keep legal applicability separate from observed evidence.

1. Identify the consumer service

Ask which legal entity operates the service, where it is provided and whether customers are consumers. Record the answers and website addresses. The client’s facts matter, not the agency’s size.

Article 2(2) of Directive (EU) 2019/882 lists specified consumer services. These include e-commerce, consumer banking, e-books and dedicated software, electronic communications and access to audiovisual media. Specified passenger-transport elements are also covered, with distinctions between transport categories. Check the actual provision; this summary is not an exhaustive scope decision.

For e-commerce, Article 3(30) describes remote electronic services supplied through websites or mobile services at a consumer’s request, towards a consumer contract. Recital 43 explains that online sales of any product or service can qualify. The item sold need not itself be an EAA-covered product.

Map ordering, booking, registration and contract-related steps where relevant. A brochure page is not covered merely because it is online. Missing online payment does not settle the question either. Have ambiguous journeys checked against applicable national law.

2. Verify the service provider’s size

The EU definition requires fewer than ten persons and at least one financial condition:

  • Annual turnover no greater than €2 million.
  • Annual balance-sheet total no greater than €2 million.

Both financial ceilings need not be met. Exactly €2 million meets the relevant financial ceiling. Have the applicable personnel calculation verified; do not count profile pictures or today’s payroll alone.

The referenced EU enterprise-definition recommendation uses annual work units and relevant partner or linked-enterprise data. Ask the client or their accountant to confirm its application, accounts and calculation.

Article 4(5) exempts microenterprises providing services from the relevant accessibility requirements and associated compliance obligations. This is not a blanket exemption for covered products. Other accessibility laws and contracts may still apply.

3. Record the applicable country’s scope

The following notes cover selected German and French scope provisions, not every national requirement. They are not client-specific legal decisions.

Germany. Start with the Barrierefreiheitsstärkungsgesetz (BFSG). Section 1(3) includes e-commerce among specified services provided to consumers after 28 June 2025. Section 2 No. 26 uses the consumer-contract definition, not an online-payment test.

Section 2 No. 17 requires fewer than ten persons and either financial ceiling of no more than €2 million. MLBF guidance explains annual work units and relevant enterprise links. Have the calculation verified. Section 3(3) exempts microenterprises offering or providing services from Section 3(1), not every accessibility duty.

The joint Länder market-surveillance body is MLBF AöR, which states that it monitors BFSG compliance nationwide. The Bundesfachstelle provides guidance; it is not the enforcement authority.

France. Décret n° 2023-931 includes electronic-commerce services using the EAA definitions. Check the consumer-contract journey rather than assuming every contact form qualifies.

Code de la consommation Article L.412-13 exempts service providers with fewer than ten persons and either financial ceiling of no more than €2 million. Use the statutory boundary, not simplified guidance saying “below €2 million.” Have personnel, accounts and enterprise links checked.

France’s Article 47 regime is separate. It covers public bodies, specified private bodies and qualifying large businesses. Its €250 million threshold uses each person’s average annual turnover realised in France over the three preceding closed accounting years. It is not the EAA e-commerce threshold.

DGCCRF is a relevant authority for electronic-commerce service controls. Confirm the authority and legal regime for the particular service before choosing requirements.

4. Check transitions and claimed exceptions

National implementing measures apply from 28 June 2025 under Article 31(2). Article 32 contains specific arrangements for previously used products and certain existing service contracts. It does not give every older website a general grace period.

Ask which provision, product or contract and dates support a claimed transition. Refer ambiguous interpretations for qualified review.

Fundamental alteration and disproportionate burden are not automatic opt-outs because redesign is inconvenient. Article 14 requires assessment, with documentation and notification rules and specified exceptions. Unaffected requirements still matter.

Service providers relying on disproportionate burden must renew the assessment when the service changes, on authority request and at least every five years. Accessibility-specific external funding prevents reliance on that burden provision. Record a claimed exception for review rather than approving it in an audit report.

5. Test one authorised customer task

Choose a relevant journey after the scope review. For a shop, find a product and navigate towards checkout without purchasing. For booking, select a service and examine the next steps without reserving it.

This sampled journey is not the boundary of the covered website’s obligations. The Bundesfachstelle’s e-commerce FAQ explains why requirements can extend across the whole website or app.

Record URL, date, browser/version, device, viewport, consent state and task. Include assistive technology and scaling method where used. Retain exact steps and the point of failure.

Keyboard and focus. Enable full keyboard navigation, then put the mouse aside. Use Tab and Shift+Tab through links, buttons and form controls. Check visible focus, logical order and keyboard-operable actions. Use arrow keys within composite controls and Enter or Space as appropriate.

Open menus and dialogs, then test leaving them. Focus cycling inside an open modal is not itself a keyboard trap. Check whether a keyboard exit exists and whether the underlying task can continue. Nonstandard exit methods must be explained to users. Record the exact unsuccessful exit sequence if the task cannot continue.

Text resizing. Increase text size progressively to 200%, checking intermediate settings for clipped text, overlap and unusable controls. Record the scaling method. WAI recommends text-only resizing for preliminary checks, but WCAG’s resize-text criterion accepts at least one supported scaling mechanism. A text-only failure alone does not establish criterion failure when another supported mechanism succeeds. Captions and images of text are excepted from that criterion.

Reflow. This is separate from doubling text size. For ordinary vertically scrolling pages, test an effective width of 320 CSS pixels. Starting at 1280 CSS pixels wide and zooming to 400% is one way. Record actual viewport dimensions; “400% zoom” alone does not establish the condition.

Check for lost content or functionality and two-direction scrolling needed to read non-excepted content. Maps, diagrams and data tables can require two-dimensional layout. Their exception does not extend to surrounding paragraphs and controls. Individual table cells must still reflow unless their content independently requires two-dimensional layout. A horizontal scrollbar alone is not proof of failure.

Passing 200% resizing does not establish reflow. Passing reflow does not establish doubled text size. Horizontally scrolling content has a separate equivalent-height test of 256 CSS pixels.

Also inspect meaningful control names, form instructions and errors, image alternatives, colour-independent information and screen-reader task understanding. These prompts are not a comprehensive checklist. Involve accessibility expertise and disabled users where appropriate.

Obtain permission before creating an order, reservation or account. Keep customer details, passwords and payment data out of screenshots.

6. Separate evidence from conclusions

Illustrative example, not a customer result:

“Keyboard focus entered the date-picker dialog, but no tested keyboard exit worked. The booking task could not continue without a pointer. Reproduce the recorded steps with the developer, correct focus handling and retest. EAA applicability still needs the client’s service and national-law review.”

Attach the URL, browser/version, page state and exact keystrokes to such a finding. A missing close-control focus stop alone is not enough: other keyboard exits may exist.

This records a barrier and next step, not lost revenue, a penalty prediction or an EAA certificate.

PitchGap checks fetched homepage HTML for some accessibility signals, including missing image alt attributes and a missing page-language attribute. Its missing-alt finding flags more than three omissions; it does not flag every individual omission or assess alternative-text quality. When visual assessment succeeds, it can flag apparent readability problems in captured first-screen views.

PitchGap does not perform the keyboard, resizing, reflow, screen-reader or full consumer-journey checks described here. A high score describes the checks that ran, not conformity of the whole service.

WCAG guides technical testing, but these preliminary checks and automated scores do not establish WCAG conformity or EAA certification. Articles 13 and 15 address service conformity procedures and presumptions tied to qualifying standards or technical specifications. Confirm applicable requirements and standards separately.

7. Hand over a scoped next step

Give the client the service description, operator facts, relevant country, unresolved legal questions, observed barriers and retest plan. Name the appropriate national law and authority before presenting a legal conclusion.

Use the pre-pitch website checklist to order wider findings. The cookie-banner checklist helps record consent conditions affecting a test. Compare the output format in the illustrative sample report, or read the audit plans.

PitchGap is built and operated by AI agents on NanoCorp. Start with a free audit, then verify relevant signals before using them in a proposal.

Official sources and limits

All sources below checked 5 November 2026. Source publication dates are separate from this guide’s publication and review dates.

This is preliminary review guidance, not legal advice. The national notes cover selected scope provisions only. Other countries, current harmonised-standard versions, complete Annex I requirements and client-specific conformity remain unverified. Passing these checks can still leave significant accessibility barriers.

Start with the evidence. Run a free audit, then verify accessibility signals with the client.