Accessibility Conformance Report

WCAG Edition (based on VPAT® Version 2.5)

Name of Product/Version

SentraBridge admin web app (the flow designer, connections, run history and settings that city staff use), version 0.6 (development build), November 2026.

Report Date

November 11, 2026

Product Description

SentraBridge is a web app for city and county staff who connect government systems. Staff build "flows" in a visual designer: they read records from one system, change them, and send them to another. The app also covers connections, run history, monitoring, approvals, people and settings. It runs in a desktop browser.

This report covers the signed-in web app (web/src). It does not cover:

• the marketing site;
• the public status page;
• the sandbox's pretend sign-in pages;
• third-party sign-in pages (Clerk) or other systems' own screens.

Contact Information

SentraBridge is a product of Civic Solution Partners, LLC, sold and supported in partnership with authorized reseller Computer Systems Plus, Inc. Accessibility questions and problem reports: 1-559-251-7767, or through your SentraBridge account contact.

Notes

• Not yet tested with assistive technology. We have not yet run a screen reader pass with NVDA, JAWS or VoiceOver, or tested with people who use them. The levels below come from automated checks, the accessibility tree that browsers hand to screen readers, and scripted keyboard-only tests. Treat them as a self-assessment, not an independent audit. We recommend, and plan, a human screen reader test before the first city go-live.
• What changed in version 0.6. Five criteria moved from Partially Supports to Supports: 1.3.1 Info and Relationships, 2.1.1 Keyboard and 4.1.2 Name, Role, Value (the Outline and named canvas steps), 1.4.10 Reflow (narrow-screen designer) and 1.4.11 Non-text Contrast (darker canvas colors). No criterion is now rated Partially Supports. These moves are based on automated and scripted checks only; the human screen reader test above could find problems that move some of them back.
• The flow designer is the hardest screen. It is a drag-and-drop canvas built on React Flow. This review added keyboard alternatives for the canvas tasks:
  • Add a step: press a palette item. The step is added after the selected step and wired to it.
  • Wire steps: the new Wires section in each step's settings lists the step's wires, removes them, and adds new ones. It covers which output (Yes/No, Matched/Different…) and which input (A/B).
  • Select and move steps: steps can be reached with Tab, selected with Enter, and moved with the arrow keys.
  • Delete a step: press Delete, or use the button in the step's settings.
  • Not covered: the minimap and panning with the mouse have no direct keyboard equivalent. The zoom and fit buttons work by keyboard.
• Flow outline (version 0.6). The designer has an Outline view (toolbar button, or Alt+Shift+O). It shows the whole flow as a text list in wiring order. Each step has a heading with its number, name and kind, a plain-English description, any problems, its last test counts, and its wires in and out (with output names such as Yes/No or Matched/Different, and inputs A/B). From the outline a person can open a step's settings, add a step after it (chosen from a list), rename it, move it up or down in the chain, delete it (its neighbours are wired together), add and remove wires, and run Preview. Each change is announced ("Added Filter after Changed records") and focus moves to the right place. On screens 760 pixels wide or less, the outline is the default view.
• Canvas changes (version 0.6). Each step on the canvas has an accessible name with its kind, name, summary, inputs, outputs, problems and last test result (for example "Filter: Open potholes. 1 input, from Changed 311 requests. Sends records to Shape as a visit."). Wires are named "Wire from … to …". Wire, handle and step border colors were darkened to at least 3:1. At narrow widths the step list and step settings open as drawers.
• Fixes made during this review (November 2026):
  • Brand-colored connector badges are darkened when needed so their text meets 4.5:1.
  • Canvas wire handles no longer carry ARIA labels that aren't allowed on them.
  • The designer has a page heading.
  • Palette group headings are in order.
  • A copy button has a name.
  • The People page headings are in order.
  • Every page now sets its own title.
  • There is a "Skip to main content" link.
  • Pages reflow to a single column at 320 CSS pixels wide.
  • Version 0.6: empty-state headings and console section headings are in order; action columns in tables have a hidden header; download links' names include their visible text.

Evaluation Methods Used

• Automated: axe-core 4.x through Playwright (Chromium), with the WCAG 2.0 and 2.1 A and AA rules plus best practices. Pages checked: Overview, Flows, the flow designer (empty, with a step selected and its settings open), Connections (list, "Add a connection" dialog, connection form), Run history, Run detail, Templates, Monitoring, Settings, People and System. After the fixes, axe reports no violations on any of these pages.
• Manual keyboard checks:
  • Building a flow with the keyboard only: add steps, select them, wire and unwire them.
  • Dialogs: focus moves into a dialog when it opens, Escape closes it, and focus returns to the button that opened it.
  • Focus is visible on palette items and buttons (2px outline) and on form fields (a blue border and 3px focus ring).
• Manual reflow and title checks:
  • At 320 CSS pixels wide there is no sideways scrolling on Overview, Connections and Run history. Data tables scroll inside their own box.
  • Each page has its own title.
• Code review: form labels, ARIA live regions (toasts use role="status"), landmark regions, and language of the page.
• Version 0.6 re-check (November 2026):
  • axe-core 4.11 (WCAG 2.0/2.1 A and AA plus best practices) on 43 pages and states: every app page (Overview, Approvals, Flows, Templates, Connections, Value maps, Run history, Trace, Monitoring, People, Activity), all nine Settings tabs, run detail, the "Add a connection" dialog and a connection form, the designer (canvas, step selected, outline, outline with its add forms open, outline with the data inspector, canvas after a preview), the Explain, Notifications, AI change and Version history dialogs, and all eleven SentraBridge Console pages. Result: no violations. The Promote dialog was not checked because the test workspace has no Production link.
  • Accessibility tree review (screen reader simulation): Playwright accessibility snapshots of the designer canvas, the outline, step settings, the connection form, run detail, Settings, the console and each dialog, read to confirm names, roles, headings, lists and states. This shows what a screen reader is given; it does not show how a screen reader speaks or navigates it.
  • Scripted keyboard-only test: a Playwright script that uses only the keyboard (Tab, Enter, Escape, typing, shortcuts) to turn on the outline, add three steps after the start step, choose a connection and what to read in the settings, insert a step between two others, move a step down, rename a step, add and remove a wire, run Preview and save. It then checks the saved flow has the four steps wired in the expected order, and that each change was announced. It passes at 1440 and 390 pixels wide.
  • Reflow: the designer at 320, 390 and 760 pixels wide (outline, step settings drawer, steps drawer, data inspector) has no sideways scrolling outside the canvas and data tables.
  • Contrast: wire, handle and border colors were measured against the canvas background.

Applicable Standards/Guidelines

Terms

• Supports: the functionality of the product has at least one method that meets the criterion without known defects, or meets it 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.
• Not Evaluated: the product has not been evaluated against the criterion. This term is used only for WCAG Level AAA.

WCAG 2.x Report

Table 1: Success Criteria, Level A

Table 2: Success Criteria, Level AA

Table 3: Success Criteria, Level AAA

Not evaluated.

Revised Section 508 Report and EN 301 549

Not included in this edition. The WCAG tables above are the basis for both. Request the 508 or EN 301 549 edition if a procurement needs it.

Known Issues and Plans

1. Screen reader testing by people with NVDA and JAWS (Windows) and VoiceOver (Mac and iPad) of the designer canvas and Outline, the connection form, run detail and Settings. Not done yet. It is the most important next step: the version 0.6 Supports ratings for 1.3.1, 2.1.1 and 4.1.2 rest on the accessibility tree and scripted keyboard tests, and a screen reader test may change them. Planned before the first city go-live; an independent audit is recommended.
2. Reordering in the Outline works for steps in a simple chain (one wire in, one out). Steps with two inputs (Reconcile, Join) or several outputs (If/else) are rewired with their Wires section instead.
3. The Promote dialog was not part of the axe run (no Production link in the test workspace).
4. WCAG 2.2 review: target size (2.5.8), dragging movements (2.5.7: the Wires section and palette press are the single-pointer alternatives), focus not obscured (2.4.11), accessible authentication (3.3.8).

Legal Disclaimer

This report describes SentraBridge's accessibility as assessed on the report date by the SentraBridge team. It is not a guarantee, and it will change as the product changes. "VPAT" is a registered service mark of the Information Technology Industry Council (ITI).