To save this as a PDF: use your browser's print dialog (Ctrl/Cmd + P) and choose “Save as PDF” as the destination. To request a Word (.docx) version, email interpreting@daytranslations.com.
Product information
- Product name — Day Interpreting on-demand interpretation service
- Product version — 2026.07
- Vendor — Day Translations, Inc. (d/b/a Day Interpreting), 1177 Avenue of the Americas, 5th Floor, New York, NY 10036, United States
- Report author — Day Interpreting engineering and product team (self-assessed)
- Report date — July 3, 2026
- Contact for accessibility questions — interpreting@daytranslations.com
Product description
Day Interpreting delivers on-demand professional interpretation in more than 300 languages, over the phone (OPI), by video (VRI), and inside third-party meeting platforms (Zoom App, Webex Embedded App, ChatGPT app). Customers reach interpreters through the customer portal at app.dayinterpreting.com, our toll-free IVR phone line, our mobile applications, and our meeting-platform integrations.
Applicable standards / guidelines
- WCAG 2.1 Level A and Level AA — Web Content Accessibility Guidelines, published by the W3C in June 2018. All success criteria in Levels A and AA are addressed in this report.
This VPAT does not include Level AAA criteria (evaluated informally only), Section 508, or EN 301 549 mappings. Those editions are available on request.
Evaluation methods used
- Manual code review of every customer-facing surface, mapping each WCAG 2.1 success criterion against the actual codebase.
- Manual keyboard-only navigation testing on the top five portal surfaces (dashboard, call history, settings, support, login).
- Visual contrast verification for text and non-text elements using the WebAIM contrast formula (target ≥ 4.5:1 for text at Level AA).
- Behavioural verification of ARIA state (aria-live regions, aria-pressed toggles, role=“dialog” focus trapping).
This report is a self-assessment. A third-party audit and a formal Accessibility Conformance Report (ACR) can be commissioned separately at customer request.
Terms
The terms used in the “Conformance Level” column throughout this report have the following meanings:
- Supports — the functionality of the product has at least one method that meets the criterion without known defects, or meets with equivalent facilitation.
- 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.
Principle 1 — Perceivable
| SC | Criterion | Level | Conformance | Remarks & Explanations |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Every icon-only interactive element carries an aria-label or an sr-only text alternative. Decorative icons are marked aria-hidden. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | The service does not deliver prerecorded audio or video media. Interpreter calls are live one-to-one sessions. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | No prerecorded video content. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | No prerecorded media content. |
| 1.2.4 | Captions (Live) | AA | Does Not Support | Real-time captioning is not currently offered inside VRI. Deaf and hard-of-hearing users are served by our on-demand American Sign Language interpreter pool. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | No prerecorded media content. |
| 1.3.1 | Info and Relationships | A | Supports | Semantic HTML landmarks (header, nav with aria-label, main, footer). Form fields associated with visible labels via htmlFor / id. Errors linked to inputs via aria-describedby and announced via role=alert. |
| 1.3.2 | Meaningful Sequence | A | Supports | DOM order matches visual reading order across all portal pages. |
| 1.3.3 | Sensory Characteristics | A | Supports | Instructions never rely on shape, color, or spatial location alone; call-state changes are announced with text plus color plus icon. |
| 1.3.4 | Orientation | AA | Supports | Content adapts to both portrait and landscape orientations; no orientation is locked. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Common fields (name, email, phone, address, password, organization, url, credit card) carry the standard HTML autocomplete attribute values across signup, login, settings, and billing surfaces. |
| 1.4.1 | Use of Color | A | Supports | Color is never the only visual means of conveying information; icons, text labels, and shape reinforce every status. |
| 1.4.2 | Audio Control | A | Not Applicable | No auto-playing audio on any page. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | All body and label text meets or exceeds a 4.5:1 contrast ratio; the majority of the interface exceeds the AAA 7:1 ratio after our July 2026 contrast pass. |
| 1.4.4 | Resize text | AA | Supports | Text can be scaled to 200% in the browser without loss of content or functionality; layouts use relative (rem) sizing throughout. |
| 1.4.5 | Images of Text | AA | Supports | Text is rendered as real text rather than baked into images. Icons paired with text labels use accessible icon fonts, not raster images of type. |
| 1.4.10 | Reflow | AA | Partially Supports | Portal pages reflow at 320 CSS pixels wide without horizontal scrolling. Wide data tables (call history, ledger) provide horizontal scrolling within a scroll container rather than reflowing. |
| 1.4.11 | Non-text Contrast | AA | Supports | Keyboard focus indicators use the brand blue (#1c44d6), which exceeds 3:1 against any surface colour on the portal. Interactive components are identifiable through multiple cues (shape, label, position) rather than border colour alone; primary button and toggle backgrounds meet or exceed 3:1 against adjacent surfaces. |
| 1.4.12 | Text Spacing | AA | Supports | Typography uses relative units (rem) throughout with generous default line height (1.5x). No fixed-height text containers clip content when the WCAG-mandated user-agent overrides are applied. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Hover-triggered tooltips are dismissable, do not obscure the triggering element, and remain visible while the pointer is over the tooltip. |
Principle 2 — Operable
| SC | Criterion | Level | Conformance | Remarks & Explanations |
|---|---|---|---|---|
| 2.1.1 | Keyboard | A | Supports | All portal functionality can be operated with a keyboard alone. Call controls, form submission, navigation, and dialogs all respond to Tab, Enter, Space, and Escape. |
| 2.1.2 | No Keyboard Trap | A | Supports | Focus can be moved into and out of every component. Modal dialogs (built on Radix primitives) trap focus while open and return focus to the trigger on close. |
| 2.1.4 | Character Key Shortcuts | A | Supports | No single-character keyboard shortcuts are used. |
| 2.2.1 | Timing Adjustable | A | Supports | The idle-session timeout displays a warning dialog with the remaining time and a one-click extension well before sign-out. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Non-essential motion (pulsing avatars, animated indicators) is gated behind the prefers-reduced-motion CSS media query; loading spinners are the only always-on motion and are permitted as loading indicators. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | No content flashes more than three times per second. |
| 2.4.1 | Bypass Blocks | A | Supports | A Skip to main content link is the first focusable element on every portal page. |
| 2.4.2 | Page Titled | A | Supports | Each route has a descriptive title element via Next.js metadata; the portal route group scopes titles to "Day Interpreting". |
| 2.4.3 | Focus Order | A | Supports | Focus order matches the visual reading order; skip link, header, sidebar, main content, footer. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Every link is either self-describing by text content or has an aria-label conveying its purpose. |
| 2.4.5 | Multiple Ways | AA | Supports | The portal offers a persistent sidebar, top navigation with search on relevant surfaces, and breadcrumb-style page headers. |
| 2.4.6 | Headings and Labels | AA | Supports | Section headings and form labels describe the content or purpose. Heading hierarchy follows h1 → h2 → h3 order per page. |
| 2.4.7 | Focus Visible | AA | Supports | A brand-blue focus ring is shown on every keyboard-focused interactive element. Focus is suppressed for mouse interactions per the CSS :focus-visible convention. |
| 2.5.1 | Pointer Gestures | A | Supports | All functionality is available with single-point activation; no multi-touch or path-based gestures are required. |
| 2.5.2 | Pointer Cancellation | A | Supports | Actions fire on pointer up, allowing users to cancel by moving off the target before releasing. |
| 2.5.3 | Label in Name | A | Supports | Visible label text is included in the accessible name for every labeled control. |
| 2.5.4 | Motion Actuation | A | Supports | No functionality is triggered by device motion or user motion. |
Principle 3 — Understandable
| SC | Criterion | Level | Conformance | Remarks & Explanations |
|---|---|---|---|---|
| 3.1.1 | Language of Page | A | Supports | The html element declares lang="en" on every page. |
| 3.1.2 | Language of Parts | AA | Supports | Language names in the interpreter picker are rendered in English (Spanish, Mandarin Chinese, French, etc.) rather than in the native script or spelling, so all content on English pages remains in the declared page language. |
| 3.2.1 | On Focus | A | Supports | Focus alone does not trigger a change of context. |
| 3.2.2 | On Input | A | Supports | Form controls do not trigger unexpected changes of context on input; navigation happens only on explicit submission. |
| 3.2.3 | Consistent Navigation | AA | Supports | The sidebar and header appear in the same location on every portal page. |
| 3.2.4 | Consistent Identification | AA | Supports | Icons and labels for common actions (call, hang up, mute, add participant, back to dashboard) are used consistently across all four calling modes. |
| 3.3.1 | Error Identification | A | Supports | Form errors are announced via role="alert" and linked to the offending input via aria-invalid and aria-describedby. The visual error state uses both color and text. |
| 3.3.2 | Labels or Instructions | A | Supports | Every form field has a visible label; complex fields include placeholder or helper text. |
| 3.3.3 | Error Suggestion | AA | Supports | Validation errors describe the problem and, where possible, the fix (e.g., "Enter a valid phone number", "Password must be at least 8 characters"). |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Money-moving actions (credit purchase, card charge, refund request) route through an explicit confirmation step showing the amount and card being charged. |
Principle 4 — Robust
| SC | Criterion | Level | Conformance | Remarks & Explanations |
|---|---|---|---|---|
| 4.1.1 | Parsing | A | Supports | HTML output is generated by React and follows valid syntax; no duplicate ids in rendered markup. |
| 4.1.2 | Name, Role, Value | A | Supports | Custom components expose the correct role, name, and state via ARIA attributes (aria-pressed on toggles, aria-expanded on menus, role="dialog" on custom modals). |
| 4.1.3 | Status Messages | AA | Supports | Call phase transitions (connecting, connected, interpreter joined, ended) are announced through a role="status" aria-live="polite" region. Form errors use role="alert". Toast notifications are announced through the toast library's built-in aria-live region. |
Summary of gaps
- 1.2.4 Captions (Live) — real-time captions of interpreter audio are not offered inside VRI. Deaf and hard-of-hearing users are served by our on-demand ASL interpreter pool.
- 1.4.10 Reflow — wide data tables scroll horizontally inside their container instead of reflowing to a single column.
All other Level A and Level AA success criteria are marked “Supports” or “Not Applicable” based on our self-assessment.
Roadmap
- Live captions (1.2.4) — under evaluation. Options include a third-party captioning provider integrated into the VRI stream and a live-transcript sidebar on the ChatGPT app.
- Table reflow (1.4.10) — mobile-first table variants are on the design backlog for call history and ledger surfaces.
- Third-party audit — a formal external audit and Accessibility Conformance Report (ACR) will be commissioned when enterprise procurement or a specific customer request requires one.