Every agreement and receipt, delivered accessible & compliant.
A rental agreement, terms & conditions, damage-waiver disclosure, and e-receipt are all consumer-facing legal documents. That puts them squarely inside the accessibility laws now being actively enforced. Hertz has no accessibility layer on these documents today. Lynxs delivers them WCAG 2.2 AA-conformant natively, with a VPAT.
Why this matters right now
The regulatory picture shifted in the last two years. These four regimes all reach Hertz’s consumer documents — and one of them just became enforceable.
European Accessibility Act (EAA)
Requires e-commerce and consumer services — including electronic agreements and receipts — to meet EN 301 549 / WCAG AA. Hertz’s European rental documents are in scope.
⚠ Enforceable since June 28, 2025Section 508 & VPAT
Hertz holds federal government travel contracts. 508 conformance is contractually required, and procurement routinely demands a VPAT / Accessibility Conformance Report — a document Hertz almost certainly cannot produce for its e-agreement flow.
Procurement blocker without a VPATADA Title III
Rental companies are “public accommodations.” Web-accessibility suits run in the thousands per year, and inaccessible legal documents and PDF receipts are common targets.
Active litigation exposureAODA
The Accessibility for Ontarians with Disabilities Act mandates WCAG AA for public-facing web content — covering Hertz Canada’s digital rental documents.
Standard baseline: WCAG 2.x AAWhat Lynxs delivers
Accessibility built into the document itself — not bolted on. Each item below is a concrete artifact or capability Hertz can demonstrate to auditors and renters.
The honest part — why native beats an overlay
Accessibility overlays are now a liability, not a proof of compliance
Overlay widgets (accessiBe, UserWay, AudioEye and similar) are increasingly a litigation target, not a defense. The FTC settled with accessiBe in 2025 over deceptive claims that its overlay made sites ADA/WCAG compliant; plaintiffs’ firms now specifically name sites that rely on overlays; and the accessibility community broadly opposes them. Overlays don’t fix the underlying document.
So Lynxs anchors the compliance claim on native conformance and a VPAT. A convenience widget can still sit on top for preference controls — but the defensible position is that the document itself conforms. That distinction is exactly what a sophisticated buyer’s counsel will probe.
See it live
Single H1, logical heading order, main landmark, skip link, named controls, a plain-language summary and a keyboard-navigable section navigator. Open it and run axe DevTools or Lighthouse — it passes in front of the buyer. Show, don’t tell.
Regulatory references: EAA Directive (EU) 2019/882 · Section 508 / Revised 508 Standards · ADA Title III · AODA · WCAG 2.2 AA (W3C).