Accessibility support and validation

OpsKnight implements keyboard-accessible navigation patterns, a skip-to-main link, visible focus treatment, semantic labels on many icon controls, dialog focus management, screen-reader-only text, and reduced-motion styles. These are implemented behaviors, not a claim that every workflow is conformant with every browser, device, or assistive-technology combination.

Interaction support

Use the skip link to move directly to the main content region.
Use Tab and Shift+Tab to reach controls; dialogs and sheets should expose a named surface and a close path.
Interactive notification rows support keyboard activation when they have a target. Icon-only controls include accessible names in reviewed surfaces.
Keyboard shortcuts supplement visible controls and are disabled in common text entry contexts. See Keyboard shortcuts.
Reduced-motion preferences disable or reduce selected animations through CSS; do not assume every third-party or browser animation is removed.
Status should be communicated by text/icon/state as well as color in critical reviewed workflows. Verify this in any customized theme.

Zoom, reflow, and mobile

Navigation and sheets use responsive layouts, and mobile routes provide focused operational workflows. Browser zoom, OS text scaling, long translated labels, virtual keyboards, and narrow devices can still expose local reflow issues. Test the exact pages responders will use rather than treating one responsive page as evidence for the whole product.

Organization acceptance test

Before production rollout and after a significant UI/theme upgrade:

Choose the supported browser, operating system, screen reader, magnification, voice-control, or switch-control combinations used by your responders.
Sign in, use the skip link and main navigation, search for an incident, and open the notification inbox without a pointer.
Create or open a controlled incident; acknowledge, assign, add a note, escalate, and resolve it using visible focus and announced labels.
Open and close every modal in the critical path. Confirm focus enters the surface, remains usable, and returns to a sensible trigger.
Test 200% and 400% zoom/reflow where required by your policy. Confirm that critical actions are not clipped or hidden behind fixed regions.
Enable reduced motion and high-contrast/color adjustments used by your team.
Repeat the response path on the supported mobile/PWA setup.
Record browser/AT versions, results, exceptions, owner, and retest date.

Known boundaries

Accessibility can vary across complex tables/charts, live-updating regions, drag/reorder interactions, custom dashboards, external ChatOps clients, public status-page themes, and browser/assistive-technology combinations. Charts need a textual or tabular interpretation for decisions. Live updates may require a manual refresh if an announcement is missed. Use the visible non-drag controls or documented alternative workflow when available.

Report an accessibility issue