VPAT / ACR
Accessibility Conformance Report.
VPAT® 2.5 Rev, WCAG edition, for the SentraOperator supervisor console and website.
Summary
This report covers the SentraOperator supervisor console and sentraoperator.com, evaluated against WCAG 2.2 Level A and AA.
Level A (32 criteria)
- 25Supports
- 2Partially Supports
- 5Not Applicable
Level AA (24 criteria)
- 18Supports
- 3Partially Supports
- 3Not Applicable
Product information
| Name of product | SentraOperator supervisor console and sentraoperator.com |
|---|---|
| Version | Phase 1 (November 2026) |
| Report date | November 2026 |
| Description | The web console 311 supervisors use to review calls, transcripts and recordings, manage legal holds and configure the AI phone agent, and the public marketing website. |
| Contact | [email protected] |
| Not covered | The phone conversation itself (see the accessibility statement for how the voice line supports relay, TTY and press 0), console sign-in (provided by the identity provider, evaluated at launch), and downloaded CSV/JSON exports. |
What was evaluated
- sentraoperator.com: every public page, including the blog, legal pages and the demo request form
- Supervisor console: Dashboard, Live calls, Call log (search, filters, call detail, recording player, legal hold form), Quality review placeholder, Settings (Departments, Greeting & languages, Hours, FAQ, Other agencies, Retention) and Usage
Evaluation methods
- Review of the source code against each WCAG 2.2 A and AA criterion: semantic structure, labels, names and roles, focus order, status messages, error handling, timing and motion
- Keyboard-only walkthroughs in Chrome of the console screens and the website's navigation, menu, FAQ and demo form, checking focus visibility and order
- Layout checks at 1440 px and 390 px wide, and color-contrast checks of the design tokens against 4.5:1 (text) and 3:1 (non-text)
- Not yet performed: automated axe-core runs across every page, and assistive-technology (screen reader) testing; both are planned before general availability
Testing dates: November 2026.
Applicable standards and guidelines
- Web Content Accessibility Guidelines (WCAG) 2.2, Level A and Level AA (this report)
- Criteria added in WCAG 2.1 and 2.2 are marked in the tables
- Revised Section 508 and EN 301 549 incorporate WCAG for web content; this is the WCAG edition of the VPAT
- The ADA Title II web rule (28 CFR part 35, subpart H) uses WCAG 2.1 Level AA
Terms
- Supports: the functionality has at least one method that meets the criterion without known defects
- Partially Supports: some functionality does not meet the criterion
- Does Not Support: the majority of functionality does not meet the criterion
- Not Applicable: the criterion is not relevant to the product
WCAG 2.2 Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1Non-text Content | Partially Supports | Icons are decorative and hidden from assistive technology; product illustrations on the website have text alternatives. Console charts have a text label with the total, and per-bar values are in tooltips and nearby tables; full data tables beside each chart are planned. |
| 1.2.1Audio-only and Video-only (Prerecorded) | Partially Supports | Call recordings in the console are accompanied by the call's transcript when one exists. Recordings whose transcript was deleted under the city's retention schedule have no text alternative. |
| 1.2.2Captions (Prerecorded) | Not Applicable | No prerecorded video. |
| 1.2.3Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video. |
| 1.3.1Info and Relationships | Supports | Headings, lists, tables with header cells, labeled form fields, landmarks (header, nav, main, footer) and breadcrumbs are marked up semantically. |
| 1.3.2Meaningful Sequence | Supports | Reading order follows the visual order; two-column layouts stack in source order on narrow screens. |
| 1.3.3Sensory Characteristics | Supports | Instructions don't rely on shape, color, size or position alone. |
| 1.4.1Use of Color | Supports | Status badges and outcome pills carry text labels; links in body text are distinguishable by context and focus styles; charts are labeled with text. |
| 1.4.2Audio Control | Supports | Recordings play only when the user presses play, and can be paused. |
| 2.1.1Keyboard | Supports | All controls are keyboard operable, including call-log rows (Enter opens a call) and the recording player: play/pause, skip 10 seconds, speed, and the seek bar (arrow keys move 5 seconds, Home/End jump to the start or end). Transcript timestamps are buttons that play from that point. |
| 2.1.2No Keyboard Trap | Supports | No keyboard traps found. |
| 2.1.4Character Key ShortcutsWCAG 2.1 | Not Applicable | No single-character shortcuts. |
| 2.2.1Timing Adjustable | Supports | No time limits. Signed recording links expire after five minutes, and a new link is issued each time play is pressed. |
| 2.2.2Pause, Stop, Hide | Supports | No auto-playing or moving content. Live call durations update every second as plain text, not as motion. |
| 2.3.1Three Flashes or Below Threshold | Supports | No flashing content. |
| 2.4.1Bypass Blocks | Supports | The website has a skip link; the console's navigation is a landmark followed by the main region. |
| 2.4.2Page Titled | Supports | Every website page has a unique, descriptive title. |
| 2.4.3Focus Order | Supports | Focus follows the visual order; opening the mobile menu keeps focus in sequence. |
| 2.4.4Link Purpose (In Context) | Supports | Link text describes the destination, or does so with its surrounding card or sentence. |
| 2.5.1Pointer GesturesWCAG 2.1 | Supports | No multipoint or path-based gestures. |
| 2.5.2Pointer CancellationWCAG 2.1 | Supports | Actions fire on click (up event) using native controls. |
| 2.5.3Label in NameWCAG 2.1 | Supports | Accessible names start with the visible label text. |
| 2.5.4Motion ActuationWCAG 2.1 | Not Applicable | No motion-operated functions. |
| 3.1.1Language of Page | Supports | Pages declare lang="en". |
| 3.2.1On Focus | Supports | Focus never triggers a change of context. |
| 3.2.2On Input | Supports | Changing a filter updates the call list in place; settings changes are saved only when the user presses Save changes. |
| 3.2.6Consistent HelpWCAG 2.2 | Supports | Contact and support links appear in the same place (header utility bar and footer) on every website page. |
| 3.3.1Error Identification | Supports | Demo form errors are shown next to each field in text and announced; console save errors are announced in a status message. |
| 3.3.2Labels or Instructions | Supports | Every input has a visible label; optional fields are marked. |
| 3.3.7Redundant EntryWCAG 2.2 | Supports | Multi-step processes don't ask for the same information twice. |
| 4.1.1Parsing | Not Applicable | Obsolete in WCAG 2.2 and treated as always supported. |
| 4.1.2Name, Role, Value | Supports | Native elements are used where possible; toggles use role="switch" with aria-checked; the FAQ uses details/summary; the menu button exposes aria-expanded. |
WCAG 2.2 Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4Captions (Live) | Not Applicable | No live audio is presented. Live call listen-in is not available yet. |
| 1.2.5Audio Description (Prerecorded) | Not Applicable | No prerecorded video. |
| 1.3.4OrientationWCAG 2.1 | Supports | Works in portrait and landscape. |
| 1.3.5Identify Input PurposeWCAG 2.1 | Supports | Demo form fields about the user carry autocomplete tokens (name, organization, email, tel, address-level1). |
| 1.4.3Contrast (Minimum) | Supports | Body text, muted text (#5A6B85, 5.3:1) and footer links meet 4.5:1. |
| 1.4.4Resize Text | Supports | Text resizes to 200% without loss of content. |
| 1.4.5Images of Text | Supports | Product illustrations are built in HTML and CSS, not images of text. |
| 1.4.10ReflowWCAG 2.1 | Partially Supports | The website reflows to 320 px. The supervisor console is designed for desktop use; at narrow widths its tables scroll horizontally. |
| 1.4.11Non-text ContrastWCAG 2.1 | Partially Supports | Focus indicators, buttons and input borders meet 3:1. The off state of console toggle switches is below 3:1 against white; a darker track is planned. |
| 1.4.12Text SpacingWCAG 2.1 | Supports | No fixed-height text containers clip content when spacing is increased. |
| 1.4.13Content on Hover or FocusWCAG 2.1 | Supports | Only native browser tooltips are used. |
| 2.4.5Multiple Ways | Supports | Main navigation, footer links, breadcrumbs, the blog index and sitemap.xml. |
| 2.4.6Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7Focus Visible | Supports | A 2px accent outline with 2px offset on every interactive element. |
| 2.4.11Focus Not Obscured (Minimum)WCAG 2.2 | Supports | The website's sticky header is offset with scroll padding so focused elements stay visible. |
| 2.5.7Dragging MovementsWCAG 2.2 | Supports | No dragging is required; the recording position is set with a single click. |
| 2.5.8Target Size (Minimum)WCAG 2.2 | Partially Supports | Buttons and links meet 24 by 24 CSS pixels, except the small remove (×) buttons on console request-type and holiday chips; larger targets are planned. |
| 3.1.2Language of Parts | Supports | Content is in English; Spanish greeting text in console settings is user-entered content. |
| 3.2.3Consistent Navigation | Supports | Navigation is in the same order on every page. |
| 3.2.4Consistent Identification | Supports | Components with the same function are labeled consistently. |
| 3.3.3Error Suggestion | Supports | Error messages say how to fix the problem (for example, the required format for State, or which safety line a greeting is missing). |
| 3.3.4Error Prevention (Legal, Financial, Data) | Supports | Settings changes are shown as unsaved until confirmed and can be discarded; legal holds require a reason and are reversible; every change is logged. |
| 3.3.8Accessible Authentication (Minimum)WCAG 2.2 | Not Applicable | The website has no sign-in. Console sign-in is provided by the identity provider and will be evaluated at launch. |
| 4.1.3Status MessagesWCAG 2.1 | Supports | Save confirmations and errors in the console, and demo form results, use role="status" / aria-live regions. |
WCAG 2.2 Level AAA
Not evaluated. SentraOperator targets Level AA.
Legal disclaimer
This report describes the product as of the report date, based on the evaluation above. It is provided for information and is not a warranty. Content each city enters (greetings, request types, FAQ answers) is the city's responsibility. Questions: [email protected]. See also our accessibility statement. “VPAT” is a registered service mark of the Information Technology Industry Council (ITI).