Skip to DART content

Access, devices, and languages

Use DART across supported devices. Work with local times and configured language options.

One workspace, scoped to the user

People should be able to move between work areas without learning a new set of controls. DART uses the same navigation and record controls across its work areas. Search finds records the user may read. Opening a result takes the user to the related work.

The available views depend on permissions. A responder sees different actions from a coordinator or instructor.

Search results are scoped before display. Opening a result runs the record’s own access checks again, so an older result cannot keep access after it has been revoked.

Responsive access

A responder in the field may use a different device from a coordinator at a desk. The web screens adapt to desktop and smaller displays. Tables and record dialogs keep the work together. The agency’s supported devices and browsers are tested during acceptance.

Access from outside the agency network needs an approved route. Identity and provider connections must work across that route.

On smaller screens, large tables and diagrams need their own contained scrolling. Keyboard focus, labels, dialogs, and the full task path still need device-level verification; a responsive layout alone is not an accessibility result.

Scoped offline responder access

Optional offline access prepares the responder’s own permitted open deployments. The saved copy includes relevant station, supervision, reporting, and limited check information. It is not an offline administrator account.

The feature must be enabled for the site. A session defaults to 15 minutes and cannot exceed 30. A new download revokes the prior active session; the responder can also revoke their active session.

The device stores an encrypted vault rather than a plaintext account cache. The unlock key stays in memory. This local protection does not extend the server session or make a queued action accepted.

Arrival, Availability, and Acknowledgment are the supported queued kinds. Sync checks the person, session expiry, permissions, action time, and matching input again. A changed deployment version returns Needs review instead of overwriting it.

Arrival uses the assigned station and the normal check-in rules. Offline availability becomes a new UTC request that still needs review. An acknowledgment does not accept an order or complete a daily check.

The encrypted local vault holds limited responder work. Sync still needs a live permitted session and current records; changed assignments produce Needs review instead of an overwrite.YesNoPermitteddownloadNew short-livedsessionEncrypted devicevaultKey stays in memoryQueued localactionArrival, availability,acknowledgmentSession andaccess valid?Assignment stillmatches?Normal domaincommandServer rules run againNeeds reviewChanged version orstationServer receiptNot merely a localqueue item
The encrypted local vault holds limited responder work. Sync still needs a live permitted session and current records; changed assignments produce Needs review instead of an overwrite.

Language choices and time zones

Teams may need help reading the interface in a language they use more comfortably. English is always available. The language selector can use AWS GovCloud Translate for saved interface text. Names and notes remain as written.

The agency reviews translated text for its chosen languages. Time zones remain part of scheduling and availability records.

The translation service accepts only allowlisted interface text and checks that field placeholders are preserved. It does not accept arbitrary record notes for translation. If the configured service is unavailable, the interface can retain English.

Accessibility in the delivery workflow

Users need to complete their work with the input methods and assistive tools they rely on. The interface supports keyboard use and labeled controls. Guided help points to the real work screen.

Section 508 review tests complete workflows with the required tools. Its report must state which version was tested. Automated checks alone do not establish agency acceptance.

Acceptance should name the actual browser, assistive tool, role, and application version. Test completing and rejecting a task, not just reaching its first button. Record any remaining barriers with the tested scope.