← Back to F18

Accessibility statement

Draft for review — not a final policy. Details marked [TO COMPLETE] must be filled in and the text reviewed by a qualified professional before publication.

Draft date: October 2026

1. Commitment

We aim to make F18 usable by everyone. This statement describes only adjustments that have actually been made and checked. A formal conformance audit against a standard such as WCAG 2.1 AA has not been performed: [TO COMPLETE when an audit is done].

2. Adjustments made

The interface, messages and these documents are available in 16 languages, with right-to-left layout for Hebrew and Arabic and the page language declared for assistive technology.

Controls are standard buttons, links and form fields with visible text labels. Selected options are exposed as pressed or checked, and validation errors and save status are announced as status messages.

Confirmation is requested before permanent deletion.

Layouts adapt to desktop and mobile widths without horizontal scrolling in the screens we checked.

The My agents screen and the policy pages were checked with an automated accessibility tool (axe-core, WCAG 2 A/AA rules) in English and Hebrew; the issues found, including insufficient button colour contrast, were fixed.

Prompts and recovery keys can be copied and downloaded as plain text files.

3. Known limitations

Testing with specific screen readers and full keyboard-only testing of every screen have not yet been completed. The cockpit home screen has not been checked with the automated tool. Automated tools find only part of possible barriers.

4. Contact

If you meet an accessibility barrier, contact the accessibility coordinator: [TO COMPLETE: name, email, phone].

Details to complete

  • • Operator legal name, registration number and postal address
  • • Contact address for privacy, accessibility and general requests
  • • Accessibility coordinator name and contact details
  • • Rights holder of the software and design
  • • Governing law and jurisdiction
  • • Legal basis for processing under the applicable law
  • • Confirmation from Lovable of sub-processors and transfer safeguards
  • • Website hosting/edge provider, its locations and any technical cookies it sets
  • • Retention of inactive histories, provider logs and backups
  • • Result of a formal accessibility audit, if performed