Standards (WCAG 2.1 AA)
Laundryless targets WCAG 2.1 Level AA for the public site, aligned with AODA expectations for Ontario. The site uses semantic landmarks, labelled forms, visible focus, skip-to-content links, text alternatives for meaningful images, keyboard-operable controls, and form status messages that do not rely on colour alone.
The public site is designed for mobile from the first pass. Interactive controls are intended to meet the 44 by 44 pixel touch target rule on small viewports. Text contrast is checked against our colour system, and the public site uses light mode only so you see a predictable, readable page.
Accessibility is part of the service. You should be able to check the service area, compare prices, read policies, book a pickup, and contact support without depending on a mouse, a large screen, animation, or a visual-only signal.
Conformance Self-Assessment
We test the site with automated accessibility checks, keyboard tests, and visual review. This statement reflects the site as reviewed on May 9, 2026. We run the tests against the same version of the site that you see.
Automated checks cannot prove every accessibility requirement. They are paired with manual review expectations: keyboard tab order, visible focus, responsive layout, no incoherent overlap, text overflow checks, image framing checks, and form state review. We repeat these checks after major design changes.
We review the booking, account, and contact forms closely, because labels, field grouping, status messages, file controls, and step announcements are what you interact with. Checks on our side add another layer, but they do not replace an accessible form.
Known Limitations
Some steps, such as verifying your email, saving a card at booking, and uploading files, get their own accessibility review whenever they change. The secure card form comes from our payment provider, so we have less control over how it is built.
The site and service are in English only for now. The French option in the language switcher is turned off, with a short note, so you are not sent to unfinished pages.
We are still reviewing blog posts, customer reviews, and images for descriptive headings, useful link text, meaningful alt text, plain language, and reading order.
Feedback Process
Accessibility feedback can be sent through the contact page or by email at info@laundryless.ca. Please include the page, browser, device, and assistive technology if relevant. A short description of what you expected, what happened, and what blocked you is enough to start the review.
Support response target is within 48 business hours. Accessibility feedback is handled through that same service path. If the issue stops you from booking, checking the service area, or using the contact form, please say so, and we will deal with it before less blocking issues.
Laundryless may ask for more detail if the report cannot be reproduced. You do not need to share private medical information or personal documents to report an accessibility issue. The goal is to understand the barrier and fix the experience.
AODA Compliance Statement
Laundryless aims to keep its customer-facing service accessible. Our target is WCAG 2.1 Level AA. This statement does not claim that every part of the customer account has been fully reviewed yet.
Accessibility is not a one-time checklist. It covers our wording, navigation, forms, keyboard access, error messages, emails, and how support responds. We check it again whenever one of these changes.
When we find a barrier, we fix it right away where we can. If a fix takes longer, we list it here as a known issue with a practical workaround. Passing automated tests is never a reason to ignore a reported barrier.
Review Schedule
Last reviewed: May 9, 2026. We review this statement again after any major change to the site, such as new forms, new navigation, new media, new language support, or new analytics or security tools.
Each review covers automated test results, keyboard navigation, mobile layout, reduced-motion behaviour, image alt text, heading structure, how readable the policies are, and how easy it is to recover from a form error.
We keep a record of what each review tested. If something could not be tested, we note it instead of marking the review complete.
