Accessibility

Inclusive experiences, explained in plain language.

We design RunSeal so reviewers, operators, and auditors can engage with confidence regardless of device, input method, or level of technical familiarity. Accessibility is an ongoing practice, not a one-time checklist.

Plain-language commitment

Product copy favours concise, jargon-free explanations with layered detail for specialised audiences. Every release includes human review to remove ambiguous phrasing, provide context for acronyms, and surface next steps without requiring tooltips.

Compatibility notes

Supported browsers

RunSeal supports the two most recent versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.

Assistive technology

We routinely verify navigation with screen readers, including VoiceOver and NVDA, and ensure semantic HTML landmarks.

Responsive layouts

Core workflows are tested at small, medium, and large breakpoints so content remains legible and actionable.

Keyboard and focus standards

  • All interactive elements are reachable and operable via keyboard-only input with visible focus states.
  • Shortcut patterns avoid conflicts with assistive technologies and include alternate menu paths.
  • Interactive sequences are linear and skip links are provided on primary pages for faster navigation.

Contrast practices

  • Text and interactive controls meet or exceed WCAG 2.2 AA contrast ratios (4.5:1 for body copy, 3:1 for large text).
  • Non-text indicators such as icons or charts pair contrast with secondary cues like shape or labels.
  • We monitor new brand assets to ensure colour pairings remain accessible across light and dark surfaces.

Requesting accommodations

If you encounter any accessibility barriers, we want to hear from you. Please reach out with your preferred communication method and we will coordinate adjustments or alternative formats.