Accessibility statement

Our commitment

rtime is committed to ensuring its scheduling features are accessible to everyone, including people who use assistive technologies such as screen readers, keyboard-only navigation, or high-contrast display modes. Accessibility is a first-class requirement, not an afterthought.

Standard applied

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We do not use automated overlay products to patch accessibility issues; all conformance work is done directly in the application code.

Measures we take

• Color contrast ratios of at least 4.5:1 for normal text (3:1 for large text).
• Color is never the only means of conveying information — all status indicators include text labels.
• All interactive elements are reachable and operable via keyboard alone.
• Visible, high-contrast focus indicators on every focusable element.
• Minimum 44 × 44 CSS pixel touch targets.
• Semantic HTML with a single H1 per page and a strict heading hierarchy.
• All form inputs have associated labels and error messages announced by screen readers.
• The availability grid supports full keyboard navigation (arrow keys + Space).
• Animations respect prefers-reduced-motion.
• A skip-navigation link allows users to bypass the navigation bar.

Known limitations

We are not aware of any outstanding WCAG 2.2 AA failures at this time. As rtime is actively developed, new features are reviewed against the standard before release. If you encounter a barrier, please let us know (see below).

Report an accessibility barrier

If you encounter anything that makes rtime difficult or impossible to use, we want to know. We aim to acknowledge reports within 2 business days and resolve barriers within 30 days.