Accessibility Statement

Our commitment

Lagelia is built for attorneys and the people who work alongside them. That includes attorneys and staff who are blind or have low vision, who navigate by keyboard, who use screen readers or magnification, who have limited fine motor control, or who are sensitive to motion. A legal platform that cannot be operated by some of the profession is not finished software, and we treat accessibility defects as defects rather than as enhancements.

Standard we are working toward

WCAG 2.2 Level AA. We use it as the target for new work and as the yardstick when reviewing what already exists. We are not yet conformant, and we will not describe ourselves as conformant until an independent, comprehensive audit says so.

Measures we have taken

• Automated accessibility linting runs across both the public website and the application, covering form labelling, alternative text, keyboard operability of interactive elements, and ARIA validity.
• Form controls throughout the application were programmatically associated with their visible labels, so a screen reader announces what each field is for rather than an unlabelled text box.
• Keyboard access was added to interactive surfaces that previously responded only to a pointer, including file upload.
• Dialogs expose dialog semantics, and dismissible surfaces close with the Escape key.
• A skip-to-content link is present so keyboard users can bypass repeated navigation.
• Motion respects the operating system reduce motion setting.
• Colour is not used as the only means of conveying a citation verdict; verified, unverified, and not-checked results carry text labels.

How we test

• Automated: static accessibility analysis integrated into the codebase, run against every screen in the application and every page of this website.
• Manual: code-level review of semantics, heading structure, landmarks, focus handling, and labelling.
• Not yet performed: testing with real assistive technology by people who rely on it, and an independent third-party audit. Both are planned and neither has happened.

Known limitations

We would rather tell you these than have you discover them:

• Some interactive elements outside the core workflows still respond to a pointer but not to a keyboard. We are working through them.
• Data tables in the application do not yet carry full header associations, which can make them difficult to navigate with a screen reader.
• Colour contrast has not been comprehensively measured across every state of every component.
• Screen-reader announcement quality for dynamic updates, such as results loading, has not been verified with assistive technology.
• The application has not been tested at 200 percent browser zoom on every screen.
• Document page images rendered from filed PDFs reproduce the source document and may not contain selectable or machine-readable text.

Reporting a barrier

If any part of Lagelia prevents you from doing your work, please tell us. Include the page or screen, what you were trying to do, and the assistive technology and browser you were using if that is relevant.

Email: support@lagelia.ai

Requesting assistance or an alternative format

If you need information from Lagelia in a different format, or need help completing a task in the application, contact us at the same address and say what would work for you. We will provide the information another way rather than ask you to work around the barrier.

How we respond

• We aim to acknowledge accessibility reports within two business days.
• We aim to give an assessment, including whether we can reproduce the barrier and what we intend to do, within ten business days.
• Barriers that prevent someone from completing a core task are treated as high priority and are not queued behind feature work.
• If we cannot fix something quickly, we will tell you what the workaround is and add it to the known limitations above.

Scope of this statement

This statement covers the public Lagelia website and the Lagelia application. It does not cover documents produced by users, third-party content, or court records displayed in their original form.

Version reviewed

Reviewed at commit 2e58bbe, plus the accessibility work described above, which was not yet committed at the time of review.

Last reviewed: July 29, 2026.