Accessibility statement

Scope and legal basis of this statement

Pallas by Lonia AI is a business-to-business software tool sold to organizations. It is not a consumer product and is not a public sector body website or mobile application.

Because of that, the two frameworks that mandate a formal accessibility statement do not, by their own terms, require one from us:

• The European Accessibility Act (Directive (EU) 2019/882) targets products and services offered to consumers. Business-only tools fall outside its consumer scope under Article 2.
• The Web Accessibility Directive (Directive (EU) 2016/2102) and its statement model, Commission Implementing Decision (EU) 2018/1523, apply to public sector bodies.

We publish this statement anyway, in good faith and voluntarily, and we have structured it to the Decision (EU) 2018/1523 model so that procurement teams, public sector customers, and disabled users get the format they already know how to read. Voluntary publication does not waive any right; it reflects that we hold our own product to the same standard we help customers meet.

Compliance status

Pallas by Lonia AI is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, because of the non-compliances listed in the next section. We treat WCAG 2.2 Level AA as a floor, not a target, and we are actively resolving the remaining items. This applies to both the marketing site (pallas.lonia.ai) and the application (app.pallas.lonia.ai). The marketing site is tested by an automated gate on every release; the application's status rests on the self-assessed Accessibility Conformance Report linked below.

Reference standards we measure against:

• WCAG 2.2 Level AA (primary conformance target)
• EN 301 549 (the European standard, which incorporates WCAG 2.1 Level AA)
• Section 508 of the US Rehabilitation Act

Accessibility features in place

Non-accessible content

The content below is not yet fully accessible. For each item we give the reason and, where relevant, an accessible alternative, following the structure required by Decision (EU) 2018/1523.

a. Non-compliance with the reference standard

• Exported PDF reports generated by the application are not yet tagged to PDF/UA (ISO 14289). Reason: the current export pipeline produces visual PDFs without a full tag tree. Accessible alternative: the same report content is available as accessible HTML in the app and as CSV export, both of which are keyboard and screen-reader accessible. PDF/UA tagging is planned.

a2. Criteria we have not evaluated

Decision (EU) 2018/1523 expects unassessed content to be identified rather than left silent, so we name it. Our Accessibility Conformance Report records two success criteria as Not Evaluated. Both are WCAG 2.2 Level AAA, which is above the Level AA target this statement is written against, so neither affects our AA conformance claim. We list them because "not evaluated" is a different answer from "meets" and should not be read as either a pass or a failure.

• 2.4.12 Focus Not Obscured (Enhanced) (WCAG 2.2 Level AAA). We have verified the Level AA form of this criterion (2.4.11, Minimum), where a focused component must not be entirely hidden. The stricter AAA form, which requires that no part of a focused component is obscured by author-created content, has not been assessed across every scroll position and sticky-header combination, so we do not claim it.
• 2.4.13 Focus Appearance (WCAG 2.2 Level AAA). Our global focus indicator is a 3px outline at 3px offset, which meets the Level AA visible-focus requirement (2.4.7). The AAA criterion additionally specifies minimum indicator area and contrast-change thresholds measured per component, which we have not measured component by component.

Every other criterion in the report carries an assessed verdict. The report records no criterion as Does Not Support.

b. Disproportionate burden

We do not currently claim a disproportionate-burden exemption for any content. If that changes, we will document the specific content and the assessment here.

c. Content not within the scope of the applicable legislation

• The free-scan page loads a larger analysis script on demand when you run a scan, which can take longer on slow connections. Reason: the analysis engine is downloaded client-side at scan time to keep your page content in your own browser. The page itself, its form, and the results are keyboard and screen-reader accessible; the delay is a performance characteristic, not a barrier to the content.
• Third-party embedded widgets such as the Stripe Checkout and Cloudflare Turnstile controls are hosted and rendered by those providers. We select accessible providers and configure them for keyboard and screen-reader use, but their internal markup is outside our direct control.

If you encounter a barrier that is not listed here, please tell us using the feedback details below and we will address it and update this section.

Preparation of this statement

• This statement was first prepared on 11 August 2026.
• It was last reviewed on 15 September 2026.
• Method used: self-assessment combined with automated testing using axe-core (4.11.x) run as a build-time gate over every page of this site, operator-conducted keyboard navigation on Windows, and partial screen-reader compatibility testing with NVDA on Windows against selected pages.
• Not performed and not claimed: testing with JAWS, VoiceOver, or TalkBack, and independent third-party expert review.
• The same evaluation basis is stated in our Accessibility Conformance Report: download the Pallas VPAT 2.5 with ACR (PDF). Where this statement and that report differ, tell us at support@lonia.ai and we will correct whichever is wrong.

Feedback and contact information

If you encounter an accessibility barrier on this site or in the Pallas application, or need content in an alternative format, please reach out. We take every report seriously and will work to resolve the issue.

Email: support@lonia.ai

You can also use our contact page. Please describe the page, the barrier, and the assistive technology you were using.

Our response window is 2-3 business days. If we cannot resolve an issue immediately, we will tell you our plan and timeline.

Data privacy requests. If you want to exercise a data protection right rather than report an accessibility barrier, write to support@lonia.ai with "Privacy request" in the subject. That covers access, correction, deletion, portability, restriction, objection, and withdrawal of consent for marketing email. Every right that applies to you is named, with its legal reference and the steps for using it, in our Privacy Policy. If a barrier on this site or in the application is what is preventing you from exercising a right, tell us at the accessibility address above and we will complete the request for you by another route; an inaccessible rights process is an accessibility failure and we will treat it as one.

Enforcement procedure

If you contact us about an accessibility barrier and are not satisfied with our response, you can escalate to the relevant authority in your jurisdiction. A fuller directory of accessibility enforcement bodies is on our accessibility enforcement page.

• European Union: the national market-surveillance or accessibility-enforcement body designated in your member state under the Web Accessibility Directive or the European Accessibility Act.
• Ireland (our EU reference point): the National Disability Authority (NDA) for public sector accessibility monitoring, the Competition and Consumer Protection Commission (CCPC) as lead market-surveillance authority for products under the European Accessibility Act as transposed by S.I. No. 636 of 2023, Coimisiún na Meán for audiovisual media services, and the Data Protection Commission for related data matters.
• Germany: the Marktüberwachungsstelle der Länder für Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR) as market-surveillance authority under the Barrierefreiheitsstärkungsgesetz (BFSG), Germany's transposition of the European Accessibility Act, and the Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT-Bund) for federal public sector IT accessibility monitoring.
• United States: complaints under the Americans with Disabilities Act may be filed with the US Department of Justice; Section 508 matters may be raised with the US Access Board.
• United Kingdom: the Equality and Human Rights Commission (EHRC).
• Canada: the Accessibility Commissioner under the Accessible Canada Act (federal), or the relevant provincial body such as the AODA compliance office in Ontario.
• Australia: the Australian Human Rights Commission, under the Disability Discrimination Act 1992.

Machine-readable statement

A structured, machine-readable version of this statement is published at /.well-known/accessibility-statement.json for procurement tooling and automated compliance registers.