VeriThreat accessibility: Accessibility Conformance Report
WCAG edition, based on the ITI VPAT® 2.5Rev template. For district procurement and accessibility reviewers. Print this page or save it as a PDF.
Last updated November 7, 2026
Product information
| Name of product | VeriThreat (web application and website) |
| Version | Release of November 2026 |
| Report date | November 7, 2026 |
| Product description | A web-based behavioral threat assessment and management platform for K-12 schools: staff reporting, a public anonymous tip line, the threat assessment team's queue and case management, district administration, and the public website (verithreat.com). |
| Contact | support@verithreat.com |
Notes
- Scope: every screen of the web application used by staff, threat assessment team members, district administrators, and law enforcement partners; the public tip line (English and Spanish); and the public website.
- Not in scope: printed or saved PDF documents (case files, letters, posters, reports), which are produced by the user's browser from accessible web pages; and email notifications, which are plain text with an HTML version.
- Content added by users: text, photos, and documents that users upload are presented as they were provided. Photos use their description, or their file name, as alternative text.
- Browsers: evaluated in current Google Chrome on desktop and with mobile screen sizes.
Evaluation methods used
- Automated testing on every release: axe-core with WCAG 2.0, 2.1, and 2.2 Level A and AA rules on 36 screens across every role, the public tip line in English and Spanish, and the website. A release is blocked by any serious or critical issue.
- Automated end-to-end checks on every release: the skip link; reflow at 320 CSS pixels; the session time-limit warning; keyboard-only use of the redaction tool; and the report, tip line, and case workflows.
- Expert review: each success criterion was reviewed against the application's code and screens by the VeriThreat development team, and issues found were fixed before this report.
- Not yet done: testing with screen readers (NVDA, JAWS, VoiceOver) by people who use them, and an independent third-party audit. Both are planned, and we'll update this report when they're complete.
Applicable standards and guidelines
| Standard or guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes), Level AA (Yes), Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes), Level AA (Yes), Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes), Level AA (Yes), Level AAA (No) |
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.
WCAG 2.x report
Table 1: Success Criteria, Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Icons are labeled or hidden from assistive technology. Charts have text equivalents (each bar is labeled with its value). Uploaded photos use their description or file name as alternative text. The image redaction canvas has a text label and instructions. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The product has no audio or video content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | No video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | No video content. |
| 1.3.1 Info and Relationships (Level A) | Supports | Headings, landmarks, lists, data tables with header cells, form labels, grouped radio buttons and checkboxes, and status messages are coded semantically. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Reading and navigation order follows the visual order. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions don't rely on shape, color, size, position, or sound. |
| 1.4.1 Use of Color (Level A) | Supports | Status, urgency, and results are always shown in words as well as color. |
| 1.4.2 Audio Control (Level A) | Not Applicable | The product plays no audio. |
| 2.1.1 Keyboard (Level A) | Supports | All functionality is available from a keyboard, including the image redaction tool (Add a box; arrow keys move it, Shift+arrows resize it). |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus can always be moved away with standard keys. The session warning keeps focus in the dialog until the user responds, by design. |
| 2.1.4 Character Key Shortcuts (Level A, 2.1 and 2.2) | Supports | The product has no single-character keyboard shortcuts. |
| 2.2.1 Timing Adjustable (Level A) | Partially Supports | Sign-in sessions end for security after 8 hours; two minutes before, a dialog offers Stay signed in, which extends the session, as many times as needed. Exception: short confirmation messages (such as "Saved") disappear after a few seconds. They're announced to screen readers when they appear, and the saved result remains visible on the page. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | Nothing moves, blinks, or scrolls for more than five seconds. The page-loading bar finishes when the page arrives. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | No content flashes. |
| 2.4.1 Bypass Blocks (Level A) | Supports | A "Skip to main content" link is the first item on every page, and pages use landmarks. |
| 2.4.2 Page Titled (Level A) | Supports | Every page has a descriptive title. |
| 2.4.3 Focus Order (Level A) | Supports | Focus order follows the page's structure. Dialogs move focus to their first action. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link text, alone or with its surrounding content, describes its destination. |
| 2.5.1 Pointer Gestures (Level A, 2.1 and 2.2) | Supports | No path-based or multipoint gestures are required. Drawing a redaction box by dragging has single-pointer and keyboard alternatives. |
| 2.5.2 Pointer Cancellation (Level A, 2.1 and 2.2) | Supports | Actions happen on release, not on press. |
| 2.5.3 Label in Name (Level A, 2.1 and 2.2) | Supports | Accessible names include the visible label text. |
| 2.5.4 Motion Actuation (Level A, 2.1 and 2.2) | Not Applicable | No functionality is operated by device motion. |
| 3.1.1 Language of Page (Level A) | Supports | Pages declare English, or Spanish for staff who choose Spanish and for the Spanish tip line. |
| 3.2.1 On Focus (Level A) | Supports | Focus never changes context. |
| 3.2.2 On Input (Level A) | Supports | Changing a field never submits a form or changes context; filters and settings have a button. |
| 3.2.6 Consistent Help (Level A, 2.2) | Supports | Help and the emergency notice are in the same place on every page. |
| 3.3.1 Error Identification (Level A) | Supports | Errors are described in text next to the form and announced to screen readers. What was typed is kept. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Every field has a visible label, with instructions where needed. |
| 3.3.7 Redundant Entry (Level A, 2.2) | Supports | Information already entered isn't asked for again in the same process. |
| 4.1.1 Parsing (Level A) | Supports | For WCAG 2.0 and 2.1. This criterion is obsolete and removed in WCAG 2.2. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Controls use native HTML elements or appropriate ARIA roles, with names and states (for example, the selected view and the current filter). |
Table 2: Success Criteria, Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | No live media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | No video content. |
| 1.3.4 Orientation (Level AA, 2.1 and 2.2) | Supports | Pages work in portrait and landscape. |
| 1.3.5 Identify Input Purpose (Level AA, 2.1 and 2.2) | Supports | Fields that collect the user's own information (email, password, one-time code, name, phone, organization) identify their purpose for autofill. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text meets 4.5:1 (3:1 for large text); secondary text colors were darkened from common defaults to meet it. |
| 1.4.4 Resize Text (Level AA) | Supports | Text can be zoomed to 200% without loss of content or function. |
| 1.4.5 Images of Text (Level AA) | Supports | No images of text, apart from logos. |
| 1.4.10 Reflow (Level AA, 2.1 and 2.2) | Supports | Pages reflow to 320 CSS pixels without horizontal scrolling. Large data tables (such as the audit log) scroll horizontally within their own area, as WCAG allows for data tables. |
| 1.4.11 Non-text Contrast (Level AA, 2.1 and 2.2) | Supports | Form field borders, checkboxes, focus indicators, and chart bars meet 3:1. |
| 1.4.12 Text Spacing (Level AA, 2.1 and 2.2) | Supports | Text containers don't have fixed heights, so increased spacing doesn't hide content. The queue shortens long AI notes to two lines by design; the full text is on the report. |
| 1.4.13 Content on Hover or Focus (Level AA, 2.1 and 2.2) | Supports | Chart value tooltips appear on hover or focus, stay while the pointer is over them, and are dismissed with Escape. Other hints use the browser's native tooltip. |
| 2.4.5 Multiple Ways (Level AA) | Supports | The menu, search (for the threat assessment team), links from related records, and Help. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | A visible focus indicator (2-pixel outline) appears on every interactive element. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA, 2.2) | Supports | The page header on small screens doesn't cover focused elements; the browser scrolls focused elements into view. |
| 2.5.7 Dragging Movements (Level AA, 2.2) | Supports | Redaction boxes can be added and placed with clicks and buttons as well as by dragging; files can be chosen with a button instead of dragged in. |
| 2.5.8 Target Size (Minimum) (Level AA, 2.2) | Supports | Targets are at least 24 by 24 CSS pixels, or have enough spacing, or are inline links in text. |
| 3.1.2 Language of Parts (Level AA) | Supports | Spanish tips are marked as Spanish when shown on English pages. Other text that users type in another language isn't marked. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | The menu is the same on every page for each role. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Components with the same function are labeled the same way. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say how to fix the problem. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | Deleting or merging records requires confirmation, and saved records can be reviewed and corrected. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA, 2.2) | Supports | Sign-in works with password managers and paste; two-step codes can be pasted from an authenticator app. |
| 4.1.3 Status Messages (Level AA, 2.1 and 2.2) | Supports | Confirmations, errors, and live results (such as a screening result) are announced without moving focus. |
Table 3: Success Criteria, Level AAA
Not evaluated.
Legal disclaimer
This report describes VeriThreat's conformance as evaluated on the date above, using the methods described. It's provided for information and isn't a warranty. "VPAT" is a registered service mark of the Information Technology Industry Council (ITI).