This report covers the accessibility of your POS software interface: screen layout, payment flow, input handling, text rendering, contrast and assistive technology compatibility. The physical hardware requirements of Annex I Section I of Directive 2019/882 — such as reach ranges, physical controls, Braille markings and audio output jacks — require a separate hardware accessibility assessment that EAA-Report does not provide.
Why your European client just changed the contract
India is one of the world's largest exporters of payment software and terminal firmware. Companies in Bangalore, Hyderabad, Pune, Chennai and Noida build the software layer that runs on POS terminals deployed by European payment processors, banks and retail chains across Germany, France, Spain, Italy and the Benelux.
The European Accessibility Act places the legal obligation on the entity placing the product on the EU market — your client, not you. But every European procurement contract now includes an accessibility compliance clause. If you cannot produce a documented self-assessment proving that your software interface meets WCAG 2.1 AA under EN 301 549, your client will either delay acceptance, withhold payment, or switch to a vendor who can.
What the EAA requires from POS software interfaces
Payment flow accessibility
Every step from card insertion to receipt must be navigable without vision. EN 301 549 requires output through at least two sensory channels.
Input without fine motor precision
PIN entry, amount input and menu navigation must not require multi-touch gestures. WCAG 2.5.1 requires single-pointer operability.
Contrast and text rendering
Transaction amounts and prompts must meet minimum 4.5:1 contrast ratio. POS software often uses branded schemes that fail.
Assistive technology compatibility
Screen reader output through headphone jack or Bluetooth. WCAG 4.1.2 requires name, role and value for all interactive components.
What you deliver to your European client
Cover page
Global compliance score, verification reference, date of assessment.
Service identification and evaluation scope
Software product, deployment context, evaluation method, applicable legal framework.
Criterion-by-criterion evaluation
17 WCAG 2.1 AA criteria evaluated across four principles: Perceivable, Operable, Understandable, Robust.
W3C remediation guidance
Actionable fixes per failed criterion from W3C Understanding WCAG 2.1.
Accessibility statement
Structured declaration following Annex V of Directive 2019/882.
Legal basis and scope disclaimer
Cites Directive 2019/882, EN 301 549 V3.2.1 and applicable national transposition law.
Generated in your browser. No data leaves your device.
What it costs
Three mistakes Indian POS developers make
"We just build the software — the hardware vendor handles compliance"
The EAA covers the complete terminal. Your European client is responsible for both layers. They will require documentation from each vendor separately. If your software layer has no accessibility assessment, the entire terminal is non-compliant. You are the bottleneck.
Running an accessibility scanner and sending the output as "the report"
Automated scanners catch approximately 30% of WCAG issues. They cannot evaluate interaction flows, keyboard navigation logic, screen reader output or error handling. A European compliance team will reject a raw scanner output.
"Nobody has enforced this yet — we'll deal with it when they ask again"
The EAA has been enforceable since 28 June 2025. Your client's legal team is not waiting. The accessibility clause is already in the contract. If you delay the documentation, you delay the deployment — and your payment.
Enforcement your European client faces — and passes to you
BFSG. Up to €100,000 per individual infringement.
Law 11/2023. Very serious infractions from €90,001.
Ordonnance 2023-859.
Implementatiewet. Up to €900,000 or 1-10% of annual turnover.
Your client faces the regulatory fine. You face the contractual consequence: delayed acceptance, withheld payment, vendor replacement.
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.
Frequently asked questions — Indian POS developers
I'm based in India. Does the EAA apply to me directly?
Does this report cover the physical terminal hardware?
Can I use one report for all clients deploying the same software?
My client is asking for EN 301 549 compliance. Is that what this covers?
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