Skip to main content

Accessibility statement

Last updated: 2026-10-06

ScreenGuardian is built by one person, and accessibility is an ongoing commitment rather than a finished line. This page lists what we target, what we know is imperfect today, and how to tell us about a barrier you hit.

What we target

We aim for WCAG 2.2 Level AA on the public website (screenguardianapp.com) and a comparable level of keyboard, contrast, and screen-reader usability in the desktop application. The Web Content Accessibility Guidelines are the de-facto international standard for web accessibility; targeting AA means we cover the most common barriers for users with visual, motor, hearing, and cognitive differences.

Where we are today

  • Website: pages use semantic HTML, visible focus indicators, and labelled controls and form fields. The site respects your system's reduce-motion setting.
  • Desktop app: every control has a name screen readers read out, and the keyboard reaches every control in the order it appears. Trends use a symbol as well as a colour. Cmd+, (Ctrl+, on Windows) opens Settings.
  • Camera-based features: ScreenGuardian's core value depends on a webcam reading body landmarks. That makes the product itself less useful to people who cannot or prefer not to use a camera. We don't have a non-camera mode yet, and we don't want to claim one until it actually works.

Known limitations

  • Charts are read out with their title and a short summary (highest value and average), not point by point. Calibration and picture-in-picture are visual only.
  • We haven't tested every screen reader and browser combination. Reports from people who use them help us most.
  • Windows high-contrast mode isn't supported yet; the app uses its own light and dark themes.

Tell us if something is broken

Email support@screenguardianapp.com with the page or screen, the assistive technology you were using, and what went wrong. We read every message and reply within 5 working days.

This statement

We review and revise this statement at least once a year, and whenever a change to the product materially affects an accessibility commitment listed above. The Last updated date at the top of this page reflects the most recent revision. Statement prepared by Eric Wang, the developer of ScreenGuardian, with reference to WCAG 2.2 and the W3C accessibility-statement guidance.