Kwashly wants every traveler to be able to plan a trip and book a wash, whatever way they use the web. This statement sets out the standard we hold ourselves to, where we meet it, where we do not, and how to tell us when something gets in your way.
1. Our commitment
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across kwashly.com, the Kwashly web app and the browser extension panel. Accessibility is part of our definition of done: new interface work is reviewed against a WCAG 2.2 AA checklist before release, and an accessibility defect carries the same priority as a functional bug of the same severity.
2. Conformance status
Kwashly is partially conformant with WCAG 2.2 Level AA: most of the service meets the standard, but some parts do not yet. The known exceptions are listed below with the reason and the fix date. This assessment covers the marketing pages, sign-up and sign-in, the trip planner, the partner laundry map, checkout, the account area and the extension panel.
3. Known gaps
- Partner map keyboard panning. The partner laundry map can be focused and zoomed with the keyboard, but fine panning still needs a pointer. Arrow-key panning with a documented shortcut is targeted for the November 2026 release. Until then, every map result also appears in a list view below the map with the same filters, distances and prices, and that list is the primary presentation for screen reader users. (Fails 2.1.1 Keyboard for the map control only.)
- Two legacy PDF invoices. Invoices issued before March 2025 were generated by our previous billing system as untagged PDFs, so headings and table structure are not exposed to assistive technology. Invoices issued since then are tagged and have a text alternative. If you need an older invoice in an accessible format, email [email protected] and we will send an HTML or CSV version within two business days. (Fails 1.3.1 Info and Relationships for those documents.)
- Third-party payment iframe. Card entry is handled inside a Stripe-hosted iframe so that card data never touches our servers. We do not control its markup; in our testing, one error message inside the frame is announced late by some screen readers. We report issues to Stripe, keep our own labels and error summary outside the frame, and offer bank transfer for Kwashly Teams invoices as an alternative route to payment. (Potential failure of 4.1.3 Status Messages.)
4. What we have implemented
- A “Skip to content” link as the first focusable element on every page.
- A visible focus indicator on all interactive elements, with a minimum 3:1 contrast against its background and never removed by our styles.
- Text and interface contrast of at least 4.5:1 for body text and 3:1 for large text, icons and control boundaries.
- Semantic landmarks — header, nav, main, aside and footer — plus a logical, unbroken heading hierarchy on every page.
- Every form field has a persistent visible label, not a placeholder alone; errors appear in text beside the field and in a summary at the top of the form.
- Respect for prefers-reduced-motion: parallax, autoplaying transitions and the map fly-to animation are disabled, and essential motion becomes a simple fade.
- Full keyboard operability of navigation, the trip planner, the date picker, filters, dialogs and checkout; focus is trapped inside modal dialogs and returned to the trigger on close.
- Text resizing to 200% and reflow at 320 CSS pixels without loss of content or horizontal scrolling.
- Touch and pointer targets of at least 24 by 24 CSS pixels, adequately spaced (2.5.8 Target Size, Minimum).
- No content that depends on color alone; laundry availability, order status and price alerts each carry a text label as well as a color.
- Page titles, language attributes and descriptive link text; icon-only buttons carry accessible names.
5. How we test
Automated checks (axe-core) run on every pull request and block a merge on new violations. Because automated tools catch only part of the picture, we also run manual keyboard-only walkthroughs of five core journeys before each release: sign up, plan a trip, find a partner laundry, book a pickup slot, manage the loyalty wallet.
Assistive technology tested in the current review cycle:
- VoiceOver with Safari on macOS 15 and on iOS 18.
- NVDA 2025.2 with Firefox on Windows 11.
- TalkBack with Chrome on Android 15.
- Keyboard-only navigation in Chrome, Edge, Firefox and Safari.
- Browser zoom to 200% and 400%, plus Windows High Contrast mode.
An external accessibility consultancy audited the trip planner, checkout and extension panel in August 2026; the gaps in section 3 come from that audit and our own follow-up testing.
6. Feedback and remediation
If you hit a barrier anywhere in Kwashly, tell us and we will fix it. Email [email protected] with the page address, what you were trying to do, and the browser and assistive technology you were using. You can also call +351 210 995 340 or use our contact page.
We acknowledge every report within 10 business days with a fix, a workaround, or a dated remediation plan. Where a fix will take longer, our support team can plan a trip, book a pickup slot or apply wallet credit on your behalf by email or phone, at no extra cost and at the prices shown on our pricing page. If our response does not satisfy you, escalate to [email protected], which reaches our compliance lead.
7. Technical specifications
Accessibility of Kwashly relies on HTML, WAI-ARIA, CSS and JavaScript. We test the current and previous major versions of Chrome, Edge, Firefox and Safari, on desktop and mobile. Where JavaScript is unavailable, the marketing and policy pages remain readable and support can complete bookings manually.
8. Legal and standards framework
This statement is prepared with regard to the European Accessibility Act (Directive (EU) 2019/882), transposed in Portugal, and the harmonized European standard EN 301 549 (V3.2.1), whose web requirements incorporate WCAG Level AA. It follows the format of the model statement used under Directive (EU) 2016/2102, which we adopt voluntarily. We also track the criteria added in WCAG 2.2 — focus appearance, dragging movements, target size, consistent help and redundant entry.
9. Approval and review
This statement was approved on 12 September 2026 by the management board of Kwashly Labs, Lda., Rua da Prata 12, 2.º andar, 1100-052 Lisbon, Portugal, on the basis of the external audit completed in August 2026 and our own evaluation. We review it at least every six months, and whenever a listed gap closes or a significant interface change ships. See also our Terms of Service and Privacy Policy.