Compliance and Security
Accessibility Conformance Report (VPAT)
This is Vilulia's Accessibility Conformance Report, prepared using the Voluntary Product Accessibility Template (VPAT) version 2.5, WCAG edition. It records, criterion by criterion, how the platform measures against WCAG 2.1 Levels A and AA. Procurement teams and accessibility reviewers can use it directly; everyone else will find the plain-language version in the Accessibility Statement.
Report information
| Product name | Vilulia ADR Platform (web application) |
|---|---|
| Product version | Current release (software as a service, continuously deployed) |
| Report date | September 2026 |
| Contact | support@vilulia.com |
| Standard | WCAG 2.1, Levels A and AA |
| Evaluation method | Internal self-evaluation: manual keyboard and screen reader testing, automated accessibility checks, and contrast measurement of interface color tokens |
Self-reported assessment. This report is prepared internally by Vilulia based on manual keyboard and screen reader testing, contrast measurement, and code review. It is not a certified audit by an independent accessibility specialist. Conformance claims reflect design intent and the state of the product at the report date; they may not capture every interaction path or assistive technology combination. Procurement teams requiring a certified third-party evaluation should contact support@vilulia.com to arrange one. We update this report when material accessibility work ships and after any formal audit is completed.
How to read the conformance levels
- Supports. The functionality of the product meets the criterion without known defects.
- Partially Supports. Some functionality of the product does not meet the criterion.
- Does Not Support. The majority of product functionality does not meet the criterion.
- Not Applicable. The criterion is not relevant to the product.
Table 1: WCAG 2.1 Level A
| Criterion | Name | Conformance level | Remarks and explanations |
|---|---|---|---|
| 1.1.1 | Non-text Content | Supports | Icons carry an aria-label, or are marked aria-hidden where an adjacent text label already names the control. |
| 1.3.1 | Info and Relationships | Supports | Semantic HTML throughout, with fieldset and legend for grouped form inputs and role="log" for case chat. |
| 1.3.2 | Meaningful Sequence | Supports | DOM reading order matches the visual order on every layout. |
| 1.3.3 | Sensory Characteristics | Supports | Instructions do not depend on shape, color, size, or position alone; controls are identified by their label text. |
| 1.4.1 | Use of Color | Supports | Case status, compliance state, and validation results pair color with a shape or a text label. |
| 1.4.2 | Audio Control | Not Applicable | No audio plays automatically. |
| 2.1.1 | Keyboard | Supports | All interactive elements are reachable and operable from the keyboard; tab navigation is implemented across the application. |
| 2.1.2 | No Keyboard Trap | Supports | Focus is not trapped in any component except modal dialogs, where the trap is intentional and the dialog closes with the Escape key. |
| 2.4.1 | Bypass Blocks | Supports | A skip-to-content mechanism is present on every page. |
| 2.4.2 | Page Titled | Supports | Every page carries a descriptive document title. |
| 2.4.3 | Focus Order | Supports | Focus order follows the logical reading order of the page. |
| 2.4.4 | Link Purpose (In Context) | Supports | Link text describes its destination in the context of the surrounding content. |
| 3.1.1 | Language of Page | Supports | The html lang attribute is set from the active locale across all five supported languages. |
| 3.2.1 | On Focus | Supports | Moving focus to a component does not trigger a change of context. |
| 3.3.1 | Error Identification | Supports | Validation errors are identified in text and associated with the field at fault. |
| 3.3.2 | Labels or Instructions | Supports | Every form input has an associated label. |
| 4.1.1 | Parsing | Supports | Markup is valid HTML5 with unique element IDs and complete start and end tags. |
| 4.1.2 | Name, Role, Value | Supports | ARIA is applied per the specification; custom controls expose name, role, and state. |
Table 2: WCAG 2.1 Level AA
| Criterion | Name | Conformance level | Remarks and explanations |
|---|---|---|---|
| 1.3.5 | Identify Input Purpose | Supports | Form fields that collect name, email, telephone, and address carry the corresponding autocomplete attribute so assistive technology can prefill them. |
| 1.4.3 | Contrast (Minimum) | Partially Supports | Most text meets the 4.5:1 ratio. Some secondary and helper text uses a light gray on white at roughly 3.0:1. Remediation is in progress. |
| 1.4.4 | Resize Text | Supports | Text resizes to 200% without loss of content or functionality. |
| 1.4.5 | Images of Text | Not Applicable | Text is rendered as text, not as images. |
| 2.4.5 | Multiple Ways | Supports | Content is reachable through the navigation menu and through in-app search. |
| 2.4.6 | Headings and Labels | Supports | Pages use a semantic heading hierarchy with descriptive headings and labels. |
| 2.4.7 | Focus Visible | Supports | A visible focus indicator is present on every interactive element. |
| 3.1.2 | Language of Parts | Supports | The language attribute is updated when the active locale changes. |
| 3.2.3 | Consistent Navigation | Supports | Navigation appears in the same relative order on every page it occurs. |
| 3.3.3 | Error Suggestion | Supports | Validation messages state what is wrong and how to correct it. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Supports | Irreversible actions, including case closure, document deletion, and signature submission, require explicit confirmation. |
Remediation
The one open item recorded here (contrast on secondary text) is tracked as a defect and is being worked. Focus return on dialog close and autocomplete attributes on form fields were resolved in September 2026. This report is revised when conformance status changes.
Requesting this report in another format
If you need this report as a document for a procurement file, or need clarification on any line above, email support@vilulia.com.
Related articles
Can't find what you're looking for? Contact Support