Accessibility Statement
Last updated: August 25, 2026
At WireLang™, we believe live translation should work for everyone — including users with visual, auditory, motor, or cognitive disabilities. This page describes, honestly, where our accessibility stands today: what already works, what doesn't yet, and what we are actively fixing.
Conformance status: WireLang™ is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not yet fully conform to the accessibility standard. The table below reports our status criterion by criterion, based on a code-level self-assessment completed on August 25, 2026. A full VPAT® 2.5 Accessibility Conformance Report will be published after our upcoming assistive-technology test pass with VoiceOver (macOS) and NVDA (Windows).
How WireLang™ works with a screen reader today
WireLang™'s primary output is spoken audio: translations are played back as speech, with the original audio automatically lowered. This means the core of the product — hearing a live translation — does not depend on reading the screen. In addition:
- Sign-in and session start use standard, labeled controls, and status changes are announced via live regions.
- A global keyboard shortcut (
Ctrl/Cmd + Alt + W) starts and stops translation from anywhere, without touching the WireLang™ window. - Every session is saved with a full text transcript you can read or download afterwards.
- The in-session toolbar (pause, language, subtitles, volume) is fully labeled for assistive technology — but currently requires a mouse click to reach. A keyboard shortcut to focus it is in development (see Known limitations).
WCAG 2.1 Conformance Status
The table below reports our current status for the WCAG 2.1 criteria we have evaluated. "Partially supports" means some functionality meets the criterion and some does not; the remarks say exactly what is missing. Criteria not listed have not yet been formally evaluated.
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 1. Perceivable (Principle 1) | ||
| 1.1.1 Non-text Content (Level A) | Partially supports | Website images include descriptive alt text and decorative SVGs are hidden with aria-hidden="true". A small number of icon-only buttons in the desktop Settings window are not yet named for assistive technology; fixes are scheduled. |
| 1.2.1 Audio-only / Video-only, Prerecorded (Level A) | Supports | Recorded session recaps play back with a synchronized text transcript, and full transcripts can be read or downloaded from session history. |
| 1.2.4 Captions, Live (Level AA) | Supports | Live subtitles for translated speech are a core product function, alongside spoken audio output. |
| 1.3.1 Info and Relationships (Level A) | Partially supports | Semantic landmarks (header, nav, main, footer) are used throughout, and all website forms are programmatically labeled. The tab structure of the desktop Settings window is not yet programmatically exposed; a fix is scheduled. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | The reading order matches the visual layout order for both the website and the desktop panels. |
| 1.4.1 Use of Color (Level A) | Supports | Color is never used as the sole means of conveying status. Connection, recording, and error states are accompanied by text. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text and background color pairs are designed to meet or exceed the WCAG AA minimum of 4.5:1 in both light and dark themes. |
| 1.4.4 Resize Text (Level AA) | Partially supports | The website honors browser zoom and text scaling. The desktop application does not yet offer zoom or a text-size setting, and subtitle size presets currently top out at 21px. Application zoom and larger subtitle sizes are on the roadmap. |
| 2. Operable (Principle 2) | ||
| 2.1.1 Keyboard (Level A) | Partially supports | The website is fully keyboard operable, as are desktop sign-in and session start/stop (including the global Ctrl/Cmd + Alt + W shortcut). One known gap: the desktop in-session toolbar currently requires a mouse click to receive focus; a keyboard shortcut to focus it is in development. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus is never trapped. Panels and dialogs can be dismissed with the Escape key or standard navigation. |
| 2.4.1 Bypass Blocks (Level A) | Supports | A "Skip to main content" link is implemented at the top of every web page. |
| 2.4.2 Page Titled (Level A) | Supports | Every web page includes a unique, descriptive title. |
| 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, on both the website and the desktop application. |
| 3. Understandable (Principle 3) | ||
| 3.1.1 Language of Page (Level A) | Supports | The HTML lang attribute is set according to the localized page (e.g., lang="es"). |
| 3.2.1 On Focus (Level A) | Supports | Receiving focus does not trigger popups, navigation, or form submission. |
| 3.2.2 On Input (Level A) | Supports | Changing a form control's value does not cause an unexpected change of context. The language selector navigates only on an explicit choice (click or Enter), not while browsing options with the keyboard. |
| 3.3.2 Labels or Instructions (Level A) | Supports | All website form fields have programmatically linked labels, and form status messages are announced via live regions. |
| 4. Robust (Principle 4) | ||
| 4.1.2 Name, Role, Value (Level A) | Partially supports | The desktop session toolbar is fully labeled (role="toolbar", aria-pressed, aria-expanded, labeled sliders), and controls are native button and input elements throughout. The desktop Settings window, its tab bar, and a few icon-only buttons are not yet named for assistive technology; fixes are scheduled. |
| 4.1.3 Status Messages (Level AA) | Partially supports | Sign-in, connection, and form status are announced via role="status" live regions. Some in-session state changes in the desktop application are not yet announced. |
Known limitations
- In-session controls require a mouse to reach. The pause, language, subtitle, and volume controls are labeled for screen readers but cannot yet be focused by keyboard. A global shortcut to focus the toolbar is in development. Sessions can already be started and stopped entirely by keyboard with
Ctrl/Cmd + Alt + W. - The floating subtitle window is not exposed to screen readers. It is a click-through visual overlay. Blind users receive the same content as spoken audio in real time, and as a text transcript in session history afterwards.
- The desktop Settings window is not yet fully labeled for assistive technology.
- Limited low-vision options in the desktop app: no application zoom, no text-size setting, and no high-contrast mode yet; subtitle size currently tops out at 21px.
Roadmap
In order of priority, we are working on:
- A keyboard shortcut to focus the in-session toolbar, plus dialog focus management.
- Full labeling of the desktop Settings window.
- Low-vision support: larger subtitle sizes, application zoom, and high-contrast subtitles.
- A complete VoiceOver and NVDA test pass, after which we will publish a full VPAT® 2.5 Accessibility Conformance Report.
This page is updated as each item ships.
Feedback
We welcome feedback on the accessibility of WireLang™. If you encounter a barrier, please email support@wirelang.com — accessibility reports are prioritized, and we aim to respond within 2 business days.
*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, based on internal self-assessment. Sevillano Consulting LLC reserves the right to modify the software specifications at any time.