This report covers your POS terminal's software interface: payment screen flow, PIN prompt display, configuration menu, receipt confirmation, error messages, merchant setup wizard. The physical hardware requirements of Annex I Section I of Directive 2019/882 require a separate hardware accessibility assessment that EAA-Report does not provide.
Why Indian POS manufacturers are receiving EAA clauses in 2025 procurement contracts
India manufactures a significant share of POS terminals deployed in European retail and banking. The EAA does not directly obligate the Indian manufacturer — the obligation falls on the entity placing the product on the EU market. But every European procurement RFP now includes an EAA accessibility compliance clause. No documentation from the manufacturer, no purchase order.
What your European buyer audits in your POS software
Payment flow screens
Transaction amounts, PIN prompts and confirmations must support non-visual output. EN 301 549 requires at least two sensory channels.
Input handling
All menu functions must be operable via external keyboard or physical keys. WCAG 2.1.1.
Screen contrast
All text must meet 4.5:1 contrast. WCAG 1.4.3.
Error and timeout handling
Declined transactions must be announced, not just displayed. WCAG 4.1.3, 2.2.1.
What you attach to the shipment documentation
Cover page
Compliance score, verification reference, date.
Identification and scope
Product, deployment context, evaluation method, legal framework.
17 WCAG 2.1 AA criteria
Criterion-by-criterion evaluation across four principles.
W3C remediation guidance
Actionable fixes per failed criterion.
Accessibility statement
Following Annex V of Directive 2019/882.
Legal basis and scope disclaimer
Directive 2019/882, EN 301 549 V3.2.1, national transposition.
What it costs
Three mistakes Indian POS manufacturers make
"We just make the hardware — the European brand handles compliance"
Your European buyer cannot certify the terminal without your software assessment. If you are the OEM, the documentation starts with you.
Testing the merchant-facing UI, ignoring consumer-facing payment flow
The consumer-facing screens are the ones the EAA cares about. If you only assess the back-office UI, you miss the entire scope.
Sending Lighthouse output as the report
Automated tools catch ~30% of WCAG issues. Your buyer's compliance team requires a structured criterion-by-criterion assessment.
Enforcement your European buyer faces
BFSG. Per-infringement fines.
Law 11/2023.
Ordonnance 2023-859.
Implementatiewet. Up to 10% of turnover.
Your buyer absorbs these fines. Your exposure: lost contract, replaced vendor, blocked shipment.
What EAA-Report guarantees and what it doesn't
EAA-Report generates a document structured under Art. 13.2 of Directive (EU) 2019/882 based on the information you enter. The truthfulness, accuracy and completeness of that information is your responsibility as the service provider or software vendor.
We guarantee that the document structure follows Art. 13.2 of Directive (EU) 2019/882 and that the legal references cited are correct as of the latest verification date. We do not guarantee that a specific document will be accepted by a market surveillance authority in a specific case, nor by a commercial buyer in a procurement process.
EAA-Report is not legal advice. For specific situations, consult a lawyer or specialised regulatory consultancy.
FAQ — Indian POS terminal manufacturers
Does this report cover the hardware?
My client is in Germany. Does this satisfy the BFSG?
Am I directly obligated as an Indian manufacturer?
Can I use one report for all deployments with the same software?
How long does it take?
Is this a certified audit?
⚠️ Important notice: EAA-Report is a self-assessment documentation tool, not legal advice and not a third-party audit. The document is generated from your input data. You are responsible for the accuracy of the data you provide. EAA-Report does not replace a qualified professional assessment.
Official legal sources
- Directive (EU) 2019/882 — European Accessibility Act — full text