Legal

Accessibility statement

We design anyping to be usable by as many people as possible — including people who rely on assistive technology.

Last updated May 7, 2026

1. Our commitment

anyping is committed to making our marketing site, application, and status pages accessible to people with a wide range of abilities. Accessibility isn't a feature we bolt on; it's a quality bar we hold the product to. We design and build with the assumption that every page will be navigated by keyboard, read aloud by a screen reader, used at 200% zoom, and viewed in high-contrast mode — because some portion of our users always will be.

2. Conformance target

We aim for WCAG 2.2 Level AA conformance across the marketing site (anyping.com), the application (app.anyping.com), and any public status pages we host. Where the spec offers AAA upgrades that don't conflict with the rest of the design, we adopt them too.

We don't claim full conformance. New features ship continuously, and accessibility is something we measure, fix, and re-measure rather than declare "done." This page reflects the current state honestly.

3. What we've done

  • Semantic HTML — landmark regions, heading hierarchy, and ARIA roles are used where native HTML doesn't already convey the meaning.
  • Keyboard navigation — every interactive element is reachable and operable with a keyboard. Visible focus styles are never removed.
  • Screen-reader labels — icons and decorative graphics carry aria-hidden; informative ones include accessible names. Form fields have explicit <label> associations.
  • Color contrast — body text meets or exceeds 4.5:1 against its background, large text and UI components meet 3:1, and we don't rely on color alone to convey meaning (status icons pair color with shape and label).
  • Motion — animations respect prefers-reduced-motion; the live ticker and pulse indicators stop animating for users who request reduced motion.
  • Zoom & reflow — layouts reflow cleanly down to 320 px wide and up to 200% browser zoom without horizontal scrolling or content loss.
  • Forms — required fields are programmatically marked, error messages are announced, and we never use placeholder text as a substitute for a label.

4. Known limitations

We're aware of the following barriers and are actively working on them:

  • Some marketing-site illustrations (status-page mockups, code panels) communicate information visually that we have not yet fully described in adjacent text. Screen-reader users get the surrounding context but may miss the visual nuance.
  • Embedded third-party widgets — if and when we add them — may not meet our internal standard. We'll either fix or replace them.
  • The application's data-dense dashboards (charts, sparklines) are an ongoing focus area. Tabular alternatives are planned for every visual data summary.

5. Compatibility

We test and support recent versions of:

  • Browsers: Chrome, Edge, Firefox, Safari (last two major releases).
  • Screen readers: VoiceOver on macOS and iOS, NVDA and JAWS on Windows, TalkBack on Android.
  • Operating-system features: high-contrast mode, increased text size, reduced motion.

The site is built on standards-based HTML, CSS, and JavaScript and degrades gracefully in older browsers, but we don't actively test against versions older than 24 months.

6. Assessment approach

We combine three types of assessment:

  • Automated — axe-core runs against the marketing site and application during build; we don't merge changes that introduce new violations.
  • Manual — keyboard, screen-reader, and zoom audits run against new and changed surfaces before release.
  • External — we plan to commission a third-party WCAG audit annually starting in our first full year of operation.

7. Reporting a barrier

If you encounter something that doesn't work for you — an unlabeled control, a low-contrast element, a feature you can't reach with a keyboard, or anything else — please tell us. We treat accessibility reports as bugs and prioritize them accordingly.

Email hello@anyping.com with the subject line "Accessibility" and include:

  • The URL or screen where you ran into the issue.
  • What you were trying to do.
  • The assistive technology and browser/OS you were using, if relevant.

We aim to acknowledge accessibility reports within two business days and to communicate a fix or workaround within ten.

8. Formal complaints

If we don't respond satisfactorily, you have the right to escalate. In the United States, complaints can be filed with the U.S. Department of Justice (ada.gov/file-a-complaint). In the European Union, your national accessibility-monitoring authority handles complaints under the European Accessibility Act.

9. Changes to this statement

We update this page as the product changes. Material updates — new conformance targets, new known limitations, new compatibility commitments — bump the "Last updated" date at the top.

10. Contact

Accessibility feedback or questions: hello@anyping.com.