Skip to main content
Start free

Accessibility statement

Last updated September 24, 2026

CompleteStatus is built for the people who keep websites running, and that includes people who use screen readers, keyboards, magnification, voice control, or reduced-motion settings. This statement covers the public website (marketing pages, blog, docs, free tools), the sign-in and sign-up screens, public status pages, and the signed-in application.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We consider the service partially conformant: most of it meets the standard, and the exceptions we know about are listed below.

How we tested

Our most recent review was completed on September 24, 2026 and combined two methods:

  • Automated checks with the open-source axe-core engine (WCAG 2.0, 2.1 and 2.2 A/AA rules plus best-practice rules), run in a real headless Chromium browser against more than 40 screens: the home page, pricing, features, free tools, blog, docs, comparisons, changelog, company and legal pages, sign-in and sign-up, error pages, a public status page, and the signed-in dashboard, monitors, incidents, status pages, settings, billing and operations screens.
  • Manual checks: keyboard-only navigation (skip link, visible focus, menus, dropdowns, tabs and disclosures), form labels and error messages, heading structure and landmarks, text contrast, status shown by text as well as colour, live-update announcements, and prefers-reduced-motion support.

What we did

  • Every page has a “Skip to main content” link and consistent header, navigation, main and footer landmarks.
  • Keyboard focus is always visible, and every menu, dropdown, tab set and collapsible section works with the keyboard.
  • Text meets the 4.5:1 contrast ratio, including muted text and status badges; status pages derive readable text colours from each customer’s brand colour.
  • Up, down and degraded states are always written out in text, never shown by colour alone. Uptime bars on status pages have a text summary.
  • Form fields have labels, and error messages are announced with the field they belong to.
  • The dashboard’s 15-second live refresh announces only a change in overall status, so screen readers are not flooded.
  • Public status pages refresh every 60 seconds so they stay current during an outage; a visible control pauses and resumes this.
  • Animations respect your operating system’s reduced-motion setting.

Known limitations

These are the issues we know about. We are working on them, and we list them so you can plan around them:

  • Charts. Response-time and uptime charts in the dashboard are drawn as graphics. The key numbers they show (uptime percentages, response times, incident counts) are also available as text on the same page, but the individual data points inside a chart are not readable by screen readers.
  • Per-day uptime detail on status pages. Each service’s 90-day bar has a spoken summary (average uptime and the worst days), but the exact figure for every single day is shown in a hover tooltip, which needs a mouse.
  • LiveStatus TV walls are designed as unattended full-screen displays. They follow the same colour-plus-text rules, but they are not designed for interactive screen-reader use.
  • Third-party components. Payment pages and card fields are provided by Stripe, and the optional bot check on sign-up, password reset and waitlist forms is Cloudflare Turnstile. We do not control their markup; both vendors publish their own accessibility commitments. If a check blocks you, email us and we will help you finish sign-up another way.
  • Downloaded PDF reports are generated for printing and have not yet been reviewed with a screen reader; the same data is available as a CSV download and on screen.

Feedback and contact

If something on CompleteStatus is hard or impossible for you to use, please tell us. Email support@completestatus.com with “Accessibility” in the subject, the page address, and what happened. You can also use our contact form.

We aim to reply within 5 business days. If you need information from an inaccessible part of the service in the meantime, we will provide it in another format.

Keeping this current

We re-run the automated checks as part of our browser test suite and review this statement whenever we make significant changes to the service, and at least once a year.