Compliance and Security

Accessibility Statement

This statement applies to the Vilulia platform at vilulia.com and the application at app.vilulia.com. It was last reviewed in September 2026.

Our commitment

Vilulia is committed to making its platform accessible to people with disabilities. Dispute resolution is a setting where a participant may have no practical alternative to the software in front of them, so accessibility is treated as a requirement of the product rather than an optional enhancement.

Our target standard is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Accessibility is reviewed as part of normal development work, and the conformance status below is updated when that review changes the answer.

Conformance status

Vilulia is partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the platform meets the standard, and the specific exceptions listed below do not.

Known non-conformances currently being addressed:

Contrast on secondary text. Some helper text, timestamps, and secondary labels use a light gray on a white background that falls below the 4.5:1 contrast ratio required by WCAG 1.4.3. Remediation is in progress.

For a criterion-by-criterion breakdown, see the Accessibility Conformance Report (VPAT).

Technical approach

The platform is built as a standard web application and relies on the accessibility features browsers and assistive technology already provide:

Semantic HTML5. Headings, lists, tables, and landmark regions use the elements that describe them, so screen readers can convey document structure without extra markup.
WAI-ARIA roles and attributes where native semantics are not enough. Case chat and caucus threads use role="log" with an aria-live region so new messages are announced as they arrive. Collapsible navigation uses aria-expanded. Grouped form inputs (party selection, notification preferences, consent choices) use fieldset and legend so the group label is read with each option.
Keyboard navigation. Every interactive control is reachable and operable from the keyboard, focus order follows reading order, and modal dialogs close with the Escape key.
Touch target sizing. Interactive controls are sized for reliable use on touch devices, including the mobile views used by parties joining from a phone.
Language declaration. The lang attribute on the document is set from the active locale, so screen readers pronounce content in the right language across all five supported locales.

Requesting an accommodation

If you need an accommodation to take part in a matter hosted on Vilulia, contact support@vilulia.com. We respond within two business days. Accommodations we can arrange include:

Case documents supplied in an alternate format
Assistance configuring the platform for a screen reader or magnifier
Extended session timeouts for your account
An alternate route to complete a task that is presenting a barrier

You do not need to disclose a diagnosis to request an accommodation. Describe the barrier and what would help, and we will work out an arrangement with you and, where the request affects scheduling, with the neutral assigned to your matter.

Reporting a barrier

We want to hear about anything on the platform that blocks you. There are two ways to report it:

Use the bug report button inside the application. The report carries the page you were on, which helps us reproduce the problem.
Email support@vilulia.com. Tell us the page, the assistive technology and browser you use, and what happened.

Accessibility reports are triaged as defects, not as feature requests. We acknowledge them within two business days and tell you what we found and when we expect a fix.

Assessment and review

The conformance claim in this statement is based on internal self-evaluation: manual keyboard and screen reader testing, automated checks run against the application, and contrast measurement of the interface color tokens. This statement was last reviewed in September 2026 and is revised when the platform changes materially or when a review changes the conformance status.

Can't find what you're looking for? Contact Support