Legal
Accessibility conformance report (VPAT)
Sentra CMS’s accessibility conformance report: WCAG 2.1 A and AA and Revised Section 508, criterion by criterion.
WCAG 2.1 A and AA summary: 43 Supports · 6 Not Applicable · 1 Partially Supports.
Report information
| Product | Sentra CMS (hosted service), release of November 2026 |
|---|---|
| Report date | November 1, 2026 |
| Report format | Based on the ITI VPAT® 2.5 template, WCAG edition |
| Product description | A hosted website content management system for cities, counties, school districts and special districts. This report covers the Sentra CMS admin, where staff edit and publish, and the public pages, templates and widgets Sentra CMS provides. |
| Contact | [email protected] · (559) 251-7767 · Computer Systems Plus, Inc., 2134 North Fine Ave, Fresno, CA 93727 |
| Evaluation methods | Automated testing with axe-core 4.12 (WCAG 2.0 and 2.1, A and AA rules) on more than 60 admin screens and on published pages, in light and dark mode; the Sentra CMS publish check; reflow measured at 320 CSS pixels; and review of keyboard alternatives, focus handling, labels and status messages in the code. |
| Not covered | Content written or uploaded by agencies (pages, PDFs, video), designs agencies import, and third-party services an agency connects. The publish check reviews agency content, but conformance of that content is the agency’s responsibility. |
Applicable standards
| Standard | Included in report |
|---|---|
| WCAG 2.0 Level A and AA | Yes |
| WCAG 2.1 Level A and AA | Yes |
| WCAG 2.1 Level AAA | Not evaluated |
| Revised Section 508 (36 CFR 1194) | Yes |
| ADA Title II web rule (28 CFR 35.200, WCAG 2.1 AA) | Yes, through WCAG 2.1 AA |
Terms
- Supports: the functionality meets the criterion without known defects, or meets it with equivalent facilitation.
- Partially Supports: some functionality doesn’t meet the criterion.
- Does Not Support: most functionality doesn’t meet the criterion.
- Not Applicable: the criterion isn’t relevant to the product.
WCAG 2.1 Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Icons have text labels or are hidden from screen readers. Images in the admin have alt text. Published pages: The publish check blocks images without alt text and flags file-name alt text. AI suggestions must be confirmed by an editor. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The admin has no prerecorded audio or video. Published pages: Agencies provide transcripts for media they upload. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The admin has no prerecorded video. Published pages: The publish check blocks video without a captions track. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The admin has no prerecorded video. Published pages: Agencies provide descriptions for video they upload. |
| 1.3.1 Info and Relationships | Supports | Headings, landmarks, lists, labeled fields, fieldsets and table headers are marked up semantically. Published pages: The publish check verifies heading order, a single H1, labeled fields and table headers. |
| 1.3.2 Meaningful Sequence | Supports | Reading order matches the visual order. Published pages: Templates keep source order equal to visual order. |
| 1.3.3 Sensory Characteristics | Supports | Instructions don’t rely on shape, color, size or position alone. |
| 1.4.1 Use of Color | Supports | Status is shown with text and icons as well as color. |
| 1.4.2 Audio Control | Supports | Nothing plays sound automatically. Published pages: The publish check blocks autoplaying video. |
| 2.1.1 Keyboard | Supports | All functions work from a keyboard. Drag and drop has keyboard alternatives: Move mode, Up and Down buttons and an Insert dialog. Scrolling regions can be focused. Published pages: Published scrolling galleries are made focusable automatically. |
| 2.1.2 No Keyboard Trap | Supports | Dialogs use the native dialog element and close with Escape. The code editor leaves Tab alone so focus can move on. |
| 2.1.4 Character Key Shortcuts | Supports | There are no single-character keyboard shortcuts. |
| 2.2.1 Timing Adjustable | Supports | Idle sign-out is set by the agency’s web admin and can be turned off. Two minutes before it happens, a dialog offers “Stay signed in”. Published pages: Published pages have no time limits. |
| 2.2.2 Pause, Stop, Hide | Supports | The admin has no moving or auto-updating content. Published pages: The publish check blocks carousels without a pause control and motion without a reduced-motion alternative. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing flashes. |
| 2.4.1 Bypass Blocks | Supports | A “Skip to content” link and landmarks are on every screen. Published pages: The default layout includes a skip link. |
| 2.4.2 Page Titled | Supports | Screens have titles that name the screen and the site. Published pages: The publish check requires a page title. |
| 2.4.3 Focus Order | Supports | Focus follows reading order. Dialogs move focus in and return it on close. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text describes its destination. Published pages: The publish check flags empty and vague links such as “click here”. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures are required. |
| 2.5.2 Pointer Cancellation | Supports | Actions run on release (standard click events). |
| 2.5.3 Label in Name | Supports | Accessible names start with the visible label. |
| 2.5.4 Motion Actuation | Not Applicable | No function uses device motion. |
| 3.1.1 Language of Page | Supports | Every screen declares its language. Published pages: The publish check requires a page language. |
| 3.2.1 On Focus | Supports | Focus never triggers a change of context. |
| 3.2.2 On Input | Partially Supports | Most settings change only when you choose Save. Some list filters (department, period) reload the list as soon as a choice is made. |
| 3.3.1 Error Identification | Supports | Errors are described in text and announced at the top of the form. Published pages: Published forms identify errors in text. |
| 3.3.2 Labels or Instructions | Supports | Every field has a visible label, and required fields are marked. Published pages: The publish check blocks unlabeled form fields. |
| 4.1.1 Parsing | Supports | Markup is valid and has no duplicate IDs. (This criterion is always satisfied under WCAG 2.2.) Published pages: The publish check flags duplicate IDs. |
| 4.1.2 Name, Role, Value | Supports | Native controls are used wherever possible. Custom controls have ARIA names, roles and states. Published pages: The publish check blocks unnamed buttons and untitled frames. |
WCAG 2.1 Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The admin has no live media. Published pages: Live meeting captions are provided by CivicCA with SentraCaptions, outside this report. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | The admin has no prerecorded video. Published pages: Agencies provide descriptions for video they upload. |
| 1.3.4 Orientation | Supports | Works in portrait and landscape. |
| 1.3.5 Identify Input Purpose | Supports | Sign-in and account fields use autocomplete (username, current and new password, name, one-time code). Published pages: Form builder email and phone fields set autocomplete. |
| 1.4.3 Contrast (Minimum) | Supports | Text meets 4.5:1 in both light and dark mode, verified with axe-core across the admin. Published pages: The theme editor checks contrast as colors are picked, and the publish check tests text contrast. |
| 1.4.4 Resize Text | Supports | Text resizes to 200% without loss of content or function. |
| 1.4.5 Images of Text | Supports | No images of text are used, except logos. |
| 1.4.10 Reflow | Supports | Screens reflow to 320 CSS pixels without horizontal page scrolling. Wide data tables scroll inside their own focusable region. |
| 1.4.11 Non-text Contrast | Supports | Form field borders, focus rings and icons that convey meaning meet 3:1 in both themes. |
| 1.4.12 Text Spacing | Supports | No loss of content when line, paragraph, letter and word spacing are increased. |
| 1.4.13 Content on Hover or Focus | Supports | Extra content shown on hover or focus can be dismissed, can be hovered over, and stays until dismissed. |
| 2.4.5 Multiple Ways | Supports | Navigation, search and the dashboard reach every screen. Published pages: Sites get menus, search and an automatically generated sitemap. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Supports | A visible focus ring is on every interactive element in both themes. |
| 3.1.2 Language of Parts | Supports | Translated content is marked with its language. Published pages: Published translations carry the right lang attribute. |
| 3.2.3 Consistent Navigation | Supports | The sidebar and top bar are the same on every screen. Published pages: Menus are shared across every page of a site. |
| 3.2.4 Consistent Identification | Supports | Icons and controls with the same function are labeled the same way. |
| 3.3.3 Error Suggestion | Supports | Error messages say how to fix the problem. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Publishing and deleting ask for confirmation. Every page has version history with restore, and publishes can be rolled back. |
| 4.1.3 Status Messages | Supports | Save confirmations and results are announced with role="status" without moving focus. |
Revised Section 508
Chapter 3, Chapter 5 (software, as an authoring tool) and Chapter 6 (support). Web content criteria in Chapter 5 are covered by the WCAG tables above.
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 302 Functional Performance Criteria | Supports | Supported through WCAG 2.1 AA conformance above, including use without vision, with limited vision, without perception of color, without hearing, with limited manipulation and with limited cognition. |
| 502 Interoperability with Assistive Technology | Supports | The admin is a web application that uses standard HTML controls and ARIA, so platform accessibility services apply. |
| 504.2 Content Creation or Editing | Supports | Editors can create content that conforms to WCAG 2.1 AA, and the publish check blocks the most serious failures. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Supports | Imported designs and pages keep alt text, labels, headings, language and ARIA attributes. |
| 504.2.2 PDF Export | Not Applicable | The admin doesn’t author PDF documents for publication. |
| 504.3 Prompts | Supports | Editors are prompted for alt text, link text, headings, captions and labels, with a “Before you publish” list and Fix buttons. |
| 504.4 Templates | Supports | Templates, starter pages and widgets provided with the product meet WCAG 2.1 AA. |
| 602.3 Electronic Support Documentation | Supports | The help center on this website meets WCAG 2.1 AA. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Supports | Available in other formats on request. |
| 603 Support Services | Supports | Support by email and phone, with information on accessibility features and alternate formats on request. |
Legal disclaimer
This report describes Sentra CMS as of the report date, based on the evaluation methods listed. It’s provided for information and isn’t a warranty. We update it when the product changes. For a signed copy or a version in another format, email [email protected].