Accessibility
Qleever Accessibility Statement
Qleever is built for customers, service providers and teams of every ability. This page explains the standard we work to, what we have built so far, what we are still fixing, and how to tell us when something gets in your way.
Our commitment
WCAG 2.2 Level AA is our engineering target.
We are working to make qleever.com conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the standard referenced by Canadian accessibility legislation, including the Accessible Canada Act and provincial frameworks in British Columbia and Ontario. Accessibility is part of our definition of done for new features, not an afterthought.
We do not claim full conformance yet. This statement describes what is implemented today, what we know still needs work, and how you can reach a person when something does not work for you.
What is built in
Accessibility features in the platform today
Keyboard operability
- Skip-to-content link on every page
- Visible keyboard focus indicator across all controls
- Menus, dialogs and forms operable without a mouse
- Escape closes dialogs and returns focus to the triggering control
Screen reader support
- Semantic landmarks: banner navigation, main content and footer
- Labelled form fields, described icon buttons and alternative text
- Live announcements for form errors, status changes and chat replies
- Dialogs announced correctly with accessible names
Visual accessibility
- Text and interface colours reviewed against WCAG 2.2 AA contrast ratios
- Content reflows on narrow screens and at browser zoom up to 200%
- Information is never communicated through colour alone
- Animations are disabled when your system requests reduced motion
Flexible access
- Fully responsive layouts for desktop, tablet and mobile
- Touch targets sized for comfortable tapping
- Guest enquiry flow available without an account
- Support and privacy requests usable without assistive barriers
Honest status
Known limitations we are working through
- Some older or provider-supplied content (profile photos, uploaded documents) may not yet have text alternatives. We review new uploads and add descriptions where we control the content.
- Third-party services embedded in workflows (payment checkout hosted by our payment provider, map or address suggestions) are outside our direct control; we choose accessible providers and raise issues with them.
- Full assistive-technology walkthroughs of every workflow are ongoing. Automated WCAG 2.2 AA checks run on our public pages as part of each release, but automation cannot catch every barrier.
Alternative access
If you cannot use part of the site, we will help another way.
You can request any Qleever service without completing the online flow. Send a guest enquiry describing what you need and our team will coordinate it with you directly.
Signed-in customers can also reach support from account support settings or the Resolution Centre.
Report a barrier
Tell us what is not working for you.
Use the form below to report an accessibility barrier — trouble booking a service, a screen reader or keyboard problem, unreadable content, an inaccessible payment form, or anything else. Choose the Accessibility barrier category so your report is routed to the team that reviews and fixes these issues. Reports go to a person; this acknowledgment is not a guaranteed resolution or response time.
This statement was last reviewed on October 22, 2026. It is updated after each accessibility audit and when platform changes affect the features described above.