Accessibility
Accessibility Conformance Report
This report shows how LEO Document Assistant meets WCAG 2.1 Level AA, the standard the ADA Title II rule requires of state and local government web content. That includes the PDFs it creates. This report is based on the VPAT 2.5 WCAG edition and covers app version 2026-10-20-tour1.
Product and evaluation
| Item | Detail |
|---|---|
| Product | LEO Document Assistant (Accusatory Instrument Builder) |
| Version | 2026-10-20-tour1 |
| Report date | 2026-10-20 |
| Vendor | Raptor Media Group LLC |
| Contact | [email protected] |
| Description | A single-file web app that runs in the browser, offline, with no outside requests. Officers use it to draft New York accusatory instruments. Screens: the document form, a live document preview, the Agency profile screen (profile and local law pack import), and a guided tour that runs on first use and reopens from Help. Output: the finished document, saved as a PDF from Chrome or Edge. |
| Standard | WCAG 2.1 Level A and AA. That is the standard the DOJ ADA Title II rule (28 CFR Part 35, Subpart H) adopts. |
| Not covered | The marketing website. The paper copy (the officer signs it in ink). |
How it was tested
- Automated: axe-core 4.10.2 with every WCAG 2.0 and 2.1 A and AA rule. Run in Chromium in six states: start, search results, charge picked, juvenile warning, blocked print, and Agency profile. 0 violations.
- Contrast: every visible text element and every form-control border was measured in light and dark themes.
- Keyboard: the whole form was walked with Tab only, and the charge list was tested with the arrow keys, Home, End, Enter and Escape.
- Reflow at 320 CSS pixels wide, and text spacing per WCAG 1.4.12.
- Scripted checks that required and missing fields are exposed to assistive technology.
- Hands-on (2026-10-20): the full screen-reader checklist with NVDA in Chrome and Edge on Windows, 200% browser zoom on a real display, and the saved PDF checked with PAC and read with NVDA in Acrobat Reader. Every step passed.
Conformance terms
- Supports: the functionality meets the criterion with no known defects.
- Partially Supports: some functionality does not meet the criterion.
- Does Not Support: most functionality does not meet the criterion.
- Not Applicable: the criterion is not relevant to the product.
WCAG 2.1 Level A
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | The logo preview has alt text. Logos next to the agency name, and the logo on the document, are marked decorative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | No audio or video. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No audio or video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No audio or video. |
| 1.3.1 Info and Relationships | Supports | Headings for each section, a main landmark, a labelled document-preview region, labels on every field, a fieldset with a legend for the mental-state choices, and a listbox for charge results. Confirmed with NVDA in Chrome and Edge. |
| 1.3.2 Meaningful Sequence | Supports | Reading order matches the visual order: form first, then the preview. |
| 1.3.3 Sensory Characteristics | Supports | Instructions name fields by their labels, not by shape, color or position. |
| 1.4.1 Use of Color | Supports | Missing fields are outlined in red and are also listed by name in a text message at the top of the form. |
| 1.4.2 Audio Control | Not Applicable | No audio. |
| 2.1.1 Keyboard | Supports | Every control works by keyboard, including file import and the charge list (arrow keys, Home, End, Enter, Escape). |
| 2.1.2 No Keyboard Trap | Supports | Focus can always leave every control by Tab or Escape. |
| 2.1.4 Character Key Shortcuts | Supports | No single-key shortcuts. The only shortcut is Ctrl+P, which uses a modifier key. |
| 2.2.1 Timing Adjustable | Supports | For privacy, the case clears after 15 minutes idle, or 2 minutes after printing. A warning appears 1 minute before, with a Keep working button, and any activity resets the timer. |
| 2.2.2 Pause, Stop, Hide | Supports | Nothing moves or auto-updates except the clear-warning countdown. That countdown is the warning itself, and it is hidden from screen readers so it doesn't repeat. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content. |
| 2.4.1 Bypass Blocks | Supports | A main landmark and section headings let users jump past the header. |
| 2.4.2 Page Titled | Supports | Title: Accusatory Instrument Builder. |
| 2.4.3 Focus Order | Supports | Tab order follows the form top to bottom. A blocked print moves focus to the first missing field. |
| 2.4.4 Link Purpose (In Context) | Not Applicable | The app has no links. |
| 2.5.1 Pointer Gestures | Supports | Only single clicks or taps. No path-based or multi-point gestures. |
| 2.5.2 Pointer Cancellation | Supports | Actions run on click (on release), not on press. |
| 2.5.3 Label in Name | Supports | Each control's accessible name begins with its visible label. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-triggered features. |
| 3.1.1 Language of Page | Supports | The page language is set to English. |
| 3.2.1 On Focus | Supports | Focus alone never changes the page. |
| 3.2.2 On Input | Supports | Choosing a charge updates the preview and may suggest a document type. If the document type conflicts with the offense level, the officer is asked; it is never changed without notice. |
| 3.3.1 Error Identification | Supports | A blocked print lists each missing item in text, marks those fields invalid for assistive technology, and moves focus to the first one. Rejected imports say why in a status message. |
| 3.3.2 Labels or Instructions | Supports | Every field has a visible label, and format hints are shown as text. A note says every field is needed to print except those marked optional. Required fields are marked for assistive technology. |
| 4.1.1 Parsing | Supports | Per the W3C 2023 errata, this criterion is always satisfied for WCAG 2.1. |
| 4.1.2 Name, Role, Value | Supports | Standard HTML controls. Collapsible sections expose an expanded state, the Agency profile button exposes a pressed state, and charge options expose a selected state. Confirmed with NVDA in Chrome and Edge. |
WCAG 2.1 Level AA
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No audio or video. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No audio or video. |
| 1.3.4 Orientation | Supports | Works in portrait and landscape. |
| 1.3.5 Identify Input Purpose | Supports | The agency name field is marked as an organization name. The other fields collect case details about other people, which this criterion doesn't cover. |
| 1.4.3 Contrast (Minimum) | Supports | Every text element measured at 4.5:1 or better in light and dark themes. |
| 1.4.4 Resize Text | Supports | The layout uses relative sizing and reflows down to 320 pixels. Confirmed at 200% browser zoom in Chrome and Edge. |
| 1.4.5 Images of Text | Supports | The only image is the agency's own logo. |
| 1.4.10 Reflow | Supports | No sideways scrolling at 320 CSS pixels wide. The document preview keeps its page layout, which this criterion exempts. |
| 1.4.11 Non-text Contrast | Supports | Field, dropdown and list borders are 3.3:1 or better against the background in both themes (fixed in this version), and the focus outline is the accent color. |
| 1.4.12 Text Spacing | Supports | No text is clipped or overlaps with WCAG text-spacing overrides applied. |
| 1.4.13 Content on Hover or Focus | Not Applicable | No tooltips or pop-ups appear on hover or focus. |
| 2.4.5 Multiple Ways | Not Applicable | A single-screen app with no set of pages to find. |
| 2.4.6 Headings and Labels | Supports | Sections and fields have descriptive headings and labels. |
| 2.4.7 Focus Visible | Supports | A 2-pixel accent outline shows on every focused control and charge option. |
| 3.1.2 Language of Parts | Supports | All content is in English. |
| 3.2.3 Consistent Navigation | Supports | The header buttons stay in the same place on every screen. |
| 3.2.4 Consistent Identification | Supports | Controls with the same function use the same names throughout. |
| 3.3.3 Error Suggestion | Supports | Messages name exactly what is missing or why a file was refused. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | The document creates a sworn legal statement. Before printing, the officer sees the complete document in the preview and must tick a Review and accept box. Any edit clears that box. |
| 4.1.3 Status Messages | Supports | Match counts, import results and pack messages are announced without moving focus. The print-blocked, juvenile, document-type and auto-clear notices are announced as alerts. Confirmed with NVDA in Chrome and Edge. |
Generated PDF
The finished document saved from Chrome or Edge is a tagged PDF. Its layout follows the established court format and is not changed for accessibility. Only invisible structure was added. The PDF was rechecked after the change, and its text and appearance are identical.
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | The agency logo is tagged as decoration, because the agency's name appears in the document text. |
| 1.3.1 Info and Relationships | Supports | Tagged PDF. The document type (for example Misdemeanor Complaint) is tagged as the main heading, and the body is tagged as paragraphs. Confirmed with PAC and with NVDA in Acrobat Reader. |
| 1.3.2 Meaningful Sequence | Supports | The tag order follows the page: caption and defendant, document type and incident number, the accusatory paragraphs, the law text, the facts, the verification notice, then the signature line. |
| 1.4.3 Contrast (Minimum) | Supports | Black text on white. |
| 2.4.2 Page Titled | Supports | The PDF title is the document type and incident number, and it is set to show in the viewer's title bar. |
| 3.1.1 Language of Page | Supports | The PDF language is set to English. |
| 4.1.2 Name, Role, Value | Not Applicable | The PDF has no form fields or links. |
Only Chrome and Edge were tested. Firefox may make untagged PDFs, so agencies should save from Chrome or Edge. The PDF is tagged but not certified to PDF/UA, which the ADA rule doesn't require.
Legal disclaimer
This report describes the accessibility of the version named above, as tested on the report date. It does not cover content an agency adds, such as its logo or the text of local law packs, or the agency's own computers, browsers and assistive technology. VPAT is a registered trademark of the Information Technology Industry Council (ITI).