Accessibility Statement

Effective date: 2026

Our commitment

Public Safety Training and Development is committed to making AgencyDoc usable by everyone who needs it, including fire-service and public-safety personnel with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and to support the accessibility expectations of Section 508 of the Rehabilitation Act.

Measures we take

Semantic HTML with landmarks, headings, lists and tables that convey structure to assistive technology. Every screen has one h1 and no skipped heading levels.
Every form control has a programmatic name, including file-upload controls inside drag-and-drop areas.
A skip link on every screen. This matters here more than on most sites: the sidebar carries your whole manual — around 300 links — ahead of the page content.
A focus indicator we designed rather than inherited, measured to stay visible on the light page and on the dark top bar alike.
Keyboard operation throughout. Navigation moves focus to the content you opened instead of returning you to the top of the page.
Progress and results announced to screen readers. Our AI features can take a minute or more, and a wait that is only shown visually is a wait a blind user experiences as silence.
Colours measured against the WCAG minimums with a contrast calculator rather than estimated by eye — for text, and for the borders and indicators that identify a control.
Layouts that reflow to a 320-pixel-wide screen without scrolling in two directions, and that respect a reduced-motion preference.
A warning ten minutes before a 12-hour session ends, with one button to stay signed in — so nobody loses unsaved work to a clock they could not see.

How we test

Four ways, because no single one is enough:

An automated WCAG 2.0/2.1 A and AA audit (axe-core) across ten screens — the public page, sign-in, the manual, agency documents, job descriptions, the Discipline Desk, user management and the administrative consoles.
A scripted keyboard walkthrough in a real browser that measures the things a rule checker cannot: where focus actually goes, whether the focus indicator is genuinely visible, whether anything can be clicked but not reached by keyboard, and how the layout behaves at 320 pixels.
A line-by-line review of the source against each criterion, which is the only way to reach states a scripted pass never sees — a panel that is closed, an error that has not happened yet, what occurs during a ninety-second wait.
An automated regression test that fails the build if one of these fixes is later removed.

We state plainly what testing does and does not prove. Automated checking detects roughly a third of accessibility problems, and the measurements above extend that but do not close the gap. None of it establishes whether a real person using a real screen reader can finish a real task. We have not completed a full walkthrough with JAWS, NVDA or VoiceOver, and we do not claim to have. A clean automated result is a floor, not a certificate.

Known limitations

Area	Status
Documents your agency uploads (contracts, policies, scanned PDFs)	These are your files, and their accessibility depends on how they were produced. A scanned or photocopied PDF has no text layer and cannot be read aloud. AgencyDoc can transcribe such a document so its text becomes available, which usually improves matters, but we cannot guarantee the original file is accessible.
Printed and exported output	Exports are generated through your browser's print function. Tagged-PDF structure for exported manuals is not yet implemented.
Screen-reader testing	Ongoing. We have not completed a full assistive-technology walkthrough of every workflow, and we do not claim to have.
Signing a document by hand	Drawing a signature freehand needs a mouse or a touchscreen. Typing your signature is offered alongside it, carries the same weight in the product, and is announced as the alternative — so signing itself never depends on being able to draw.

If something is in your way

If you meet an accessibility barrier, or need something in a different format, tell us and we will help — and fix it. Please include the screen you were on and the assistive technology you were using, because that is what makes a problem reproducible. Contact your AgencyDoc administrator, or Public Safety Training and Development directly.

For procurement

A formal Accessibility Conformance Report (VPAT 2.5, Revised Section 508 edition) is published and needs no account to read. It gives a verdict for every WCAG 2.1 A and AA criterion and for the Section 508 chapters, including the ones we do not yet meet, and it explains how each verdict was arrived at.

This statement describes our accessibility goals, the measures actually in place, and the limitations we know about — it is not a claim of full conformance.