Accessibility statement
Scene SizeUp LLC · Last updated 24 September 2026
Scene SizeUp is committed to making incident command training usable by every firefighter in a department, including those who use assistive technology.
This statement describes our conformance target, how we actually verify it, and where we currently fall short. Public agencies frequently need this on file for Section 508 and state procurement purposes.
Conformance target
Scene SizeUp aims to conform to WCAG 2.1 Level AA, and adopts the additional Level AA success criteria introduced in WCAG 2.2 where they apply, including target size and focus appearance. This is the standard referenced by Section 508 of the Rehabilitation Act.
We describe the product as substantially conformant: the criteria below are tested continuously and pass, and the known exceptions are listed openly rather than omitted.
How we verify it
Accessibility is checked automatically on every change, and a change cannot be committed if the check fails. That audit covers 23 application surfaces, signed in and signed out, including the live drill, the scenario builder, the after-action review, the training report, department administration, and the public marketing and documentation pages.
The audit has two halves.
Automated rule checking. An industry-standard rules engine runs against every surface. It currently reports zero violations across all 23. We are careful about what that means: automated tooling reliably catches only a portion of WCAG failures, which is why the second half exists.
Checks a rules engine cannot make, run against the rendered page:
- Contrast measured against what is actually behind the text, including text over photographs, gradients, and the live scene, rather than against the declared background color.
- Every keyboard focus stop has a visible focus indicator. Automated tools confirm focus is reachable; they do not confirm you can see where it is.
- Target sizes of at least 24 by 24 pixels, or a qualifying spacing exception, for every control.
- Reflow at 320 pixels wide with no horizontal scrolling, so the app is usable magnified or on a phone.
Design decisions that support this
- The interface uses a defined type scale and a named color system with recorded contrast ratios rather than ad-hoc values.
- Status is never conveyed by color alone; state is also carried in text or shape.
- Interactive controls are real buttons and links with proper roles, so the keyboard and screen readers behave predictably.
- Motion is limited, and animation respects the operating system's reduced-motion preference.
- Native form controls are used and themed rather than reimplemented.
Known limitations
We would rather list these than let you discover them after purchase.
- The photograph behind the drill scene is not described. The scene is a photograph with fire, smoke, victims, apparatus and hazards placed on top of it. Those placed elements are now read out. A screen reader announces the whole scene when you arrive on a view ("Side A: 5 things on scene. Fire, growth, high on the right. Adult, unconscious, midway up on the right...") and announces changes as they happen, so a fire being knocked down or a victim being rescued is spoken. What is still not described is the photograph itself: the building, its construction, its exposures and its surroundings. An instructor's own written briefing remains the way that reaches a crew.
- Radio is audio. Transmissions are voice. Every transmission is automatically transcribed and the transcript is part of the permanent record and the printed after-action report, but transcription is machine-generated and is not a certified caption.
- Scenario building no longer needs a pointer. This was listed here as a limitation until 24 September 2026 and is now closed. Choose a tool, press Enter to drop the element in the middle of the view, arrow it where it belongs with shift to move faster, and press plus or minus to size it, with shift for five steps at once. Elements can also be copied between views from the keyboard. One keyboard step is the same amount of change as one notch of a scroll wheel, so nothing in the builder is out of reach of a keyboard that a mouse can do.
- Positioning a rig in an apparatus placement drill still needs a pointer. An apparatus placement drill is a tabletop exercise in which the participants themselves park apparatus on the aerial photograph, which is done by dragging the rig and sizing it with a scroll gesture. The keyboard equivalents described above are in the scenario builder and do not reach this surface. Every other way of taking part in a drill, including a full drill, needs no pointer: the instructor places the scene beforehand, and participants walk between views, transmit on the radio and file reports without one.
- Mobile is landscape-first. The phone layout is designed for a landscape device. Portrait use is possible but not the primary target.
- Some documentation images lack detailed descriptions. Screenshots in the documentation carry short alternative text but not full long descriptions.
Two priority items now, both listed above. Positioning a rig in an apparatus placement drill from the keyboard, which is the narrower of the two and the one that affects a participant rather than an author. And the photograph behind the scene: the elements an instructor places on a view are read out, but the building in the picture, its construction and its surroundings are not, and no automated description can be trusted to get a building's construction right. What would close the second is a description an author writes for each view, carried to a screen reader the way the placed elements already are.
Compatibility
Scene SizeUp is a web application and is tested on current versions of Chrome, Safari, Edge, and Firefox on desktop, and Safari and Chrome on iOS and Android. It requires JavaScript. Microphone access is required to transmit on the radio, and documentation is provided for granting it on Windows and macOS.
Feedback
If you encounter a barrier, tell us and we will treat it as a defect rather than a suggestion.
Email: support@getsizeup.com with "accessibility" in the subject.
Please include the page or feature, what you were trying to do, and the assistive technology and browser you were using. We aim to acknowledge within two business days.
Formal documentation
This statement is based on our own continuous testing. A VPAT (Voluntary Product Accessibility Template) has not been completed by an independent third party. If your procurement process requires one, contact us and we will discuss it. We will not represent an untested criterion as conformant in order to complete a form.