Skip to content
Accessibility

Accessibility statement

Last updated: June 22, 2026

Schedio is committed to making our product usable by everyone, including people who rely on assistive technology. This statement explains the standard we work to, where we stand today, and how to reach us if something gets in your way.

1. The standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — the level most widely referenced by regulators and courts in the United States. Accessibility is an ongoing effort, not a one-time project: we check new pages against these guidelines and fix issues as we find them.

2. Where we stand

Our marketing site at schedio.team substantially conforms to WCAG 2.1 AA. We have verified support for full keyboard navigation with a visible focus indicator and a skip-to-content link, screen-reader landmarks and correct page-language identification, text resizing and page zoom without loss of content, sufficient colour contrast for text, and respect for the operating-system “reduce motion” setting. We are working to bring the signed-in application at app.schedio.team to the same standard.

3. Known limitations

This statement reflects our own assessment rather than a formal third-party audit or certification, so some isolated issues may remain — particularly in the more interactive parts of the signed-in application, which we are still reviewing. If you rely on a specific assistive technology and run into a barrier, tell us and we will prioritise it.

4. How we test

We combine automated checks with manual keyboard and screen-reader testing during development. If you need a deeper conformance report (for example a VPAT / Accessibility Conformance Report) for a procurement review, contact us and we will help.

5. Tell us about a barrier

If any part of Schedio is hard to use with assistive technology, email info@schedio.team with the page and what went wrong. We aim to reply within five business days and will provide the information you need in an accessible format while we fix the underlying issue.