Accessibility Statement (VPAT / ACR)
Last updated: July 23, 2026
At WireLang™, we believe that technology should be integration-first — removing the barriers between people of all backgrounds, languages, and abilities. We are committed to ensuring our website and desktop applications are accessible to everyone, including users with visual, auditory, motor, or cognitive disabilities.
This document serves as our official Accessibility Conformance Report (ACR), based on the Voluntary Product Accessibility Template (VPAT®) Version 2.4/2.5.
WCAG 2.1 Conformance Report
The table below indicates the level of conformance for each major WCAG 2.1 accessibility criteria across our web presence and desktop clients.
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 1. Perceivable (Principle 1) | ||
| 1.1.1 Non-text Content (Level A) | Supports | All decorative SVG icons in the web and desktop UI include aria-hidden="true". Product images include descriptive alt text. |
| 1.2.1 Audio-only / Video-only (Level A) | Not Applicable | The product does not serve or output prerecorded video or audio media content. |
| 1.3.1 Info and Relationships (Level A) | Supports | Semantic tags (header, nav, main, footer) are used. Form elements and range input sliders are programmatically linked to labels via aria-labelledby. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | The reading order matches the visual layout order for both the website and the desktop popover panels. |
| 1.4.1 Use of Color (Level A) | Supports | Color is never used as the sole visual means of conveying status. Connection, recording, and error details are accompanied by text descriptions and state changes. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | All text and background colors maintain contrast ratios exceeding the WCAG AA minimum of 4.5:1. |
| 2. Operable (Principle 2) | ||
| 2.1.1 Keyboard (Level A) | Supports | All interactive controls, popovers, select dropdowns, and volume sliders are accessible and triggerable via standard keyboard controls (Tab, Space, Enter). |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus is never trapped. Users can close popup panels or navigate away using standard navigation keys or the Escape key. |
| 2.4.1 Bypass Blocks (Level A) | Supports | A slide-in Skip Link (Skip to main content) is implemented at the top of the body to allow users to bypass navigation link headers. |
| 2.4.2 Page Titled (Level A) | Supports | Every web page includes unique, descriptive title tags. |
| 2.4.3 Focus Order (Level A) | Supports | The tabbing sequence follows a logical structural flow. |
| 2.4.4 Link Purpose (Level A) | Supports | Link anchors explicitly state their target destination or documentation context. |
| 2.4.7 Focus Visible (Level AA) | Supports | A high-contrast outline is styled using :focus-visible to clearly identify the active element during keyboard navigation. |
| 3. Understandable (Principle 3) | ||
| 3.1.1 Language of Page (Level A) | Supports | The HTML tag dynamically sets the lang attribute according to localized parameters (e.g., lang="es"). |
| 3.2.1 On Focus (Level A) | Supports | Focus indicators do not trigger popups or initiate form submissions. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Labels and input fields are explicitly linked programmatically. |
| 4. Robust (Principle 4) | ||
| 4.1.2 Name, Role, Value (Level A) | Supports | All custom controls utilize semantic markup or ARIA attributes (role="toolbar", aria-expanded, aria-pressed) to communicate status, name, and value to assistive technologies. |
*Disclaimer: The information contained in this document is provided in good faith and represents the current conformance state of WireLang™ Live as of the date of publication. Sevillano Consulting LLC reserves the right to modify the software specifications at any time.