Accessibility Statement

We are committed to making our platform accessible to everyone, including people with disabilities.

Our Commitment

Kaboosh is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

Kaboosh is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Accessibility Features

⌨️

Keyboard Navigation

Keyboard navigation across core study flows, with visible focus states and consistent controls.

🔊

Screen Reader Support

Screen reader support for key flows using semantic HTML and ARIA labels.

🎨

Color Contrast

Color choices are designed to meet WCAG 2.1 AA contrast targets in supported views.

📝

Text Alternatives

Alternative text for images and meaningful content for all visual elements.

📱

Responsive Design

Responsive layouts for desktop, tablet, and mobile screens.

🔊

Audio Support

Text-to-speech functionality and audio controls for enhanced accessibility.

WCAG 2.1 Guidelines

Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

•Alternative text for images
•Captions for multimedia content
•High contrast color combinations
•Adjustable text size and spacing

Operable

User interface components and navigation must be operable.

•Keyboard accessibility
•Sufficient time limits
•No content that causes seizures
•Easy navigation and search functionality

Understandable

Information and the operation of user interface must be understandable.

•Readable text content
•Predictable navigation
•Input assistance and error prevention
•Consistent and clear interface design

Robust

Content must be robust enough to be interpreted reliably by a wide variety of user agents.

•Compatibility with assistive technologies
•Semantic HTML structure
•Proper form labels and instructions
•Accessible rich internet applications (ARIA)

Accessibility Feedback

We welcome your feedback on the accessibility of our website. Please let us know if you encounter any accessibility barriers.