lovable-accessibilitylisted

# Lovable Accessibility — Israel (ת"י 5568) + EU (EAA) Lovable output starts from a good base (Radix primitives ship real ARIA, focus management, and keyboard handling) and then loses it in the generated app layer: custom `<div onClick>` controls, English `aria-label`s on Hebrew buttons, no focus management on route change, decorative heading levels, and default token contrast that misses AA. The gap is always in the code Lovable wrote around the components, not in the components. **This is engineering guidance, not legal advice.** For a business over ~5M ₪ turnover, a public body, or anyone already served with a demand letter, the deliverable is a survey by a certified מורשה נגישות שירות — this skill gets the code and the paperwork to the point where that survey passes. ## Two rules that override everything else 1. **Conformance lives in the code. A toolbar is a convenience feature, never the compliance strategy.** Never install a third-party overlay script (accessiBe / UserWay / EqualWeb auto-fix widgets) as the fix. The FTC fined accessiBe $1M in April 2025 over its compliance claims, the European Commission has stated overlays are not a valid path to conformance, and roughly a quarter of US web-accessibility suits in 2024 targeted sites that had an overlay installed. If the client already pays for one, whether to keep it is their business call — fix the code either way, and never let the widget be cited as the reason the site is compliant. 2. **Automated scores lie.**