Accessibility Statement
SudsOn this page
Accessibility Statement
SudsOn this page
Last updated: October 24, 2026
In this statement:
2.1 Goal. We want everyone to be able to book a service, pay an invoice, and run a shop on Suds, including people who use assistive technology. We treat accessibility as part of building the product, and we fix the barriers we find or are told about.
2.2 No certification claim. This statement describes our target and our current state. It is not a claim that every page fully conforms to WCAG 2.1 AA, and no third party has certified the Service. We list the gaps we know about in section 6.
3.1 Covered.
This statement covers the Service operated by Suds Software LLC at suds.com, getsuds.com, and their subdomains (including app.suds.com and app.getsuds.com), and Suds-hosted pages served on a Business’s own domain. That includes:
3.2 Not covered. A Business’s own website or social pages that Suds does not host, and third-party sites you reach from the Service, are outside this statement. Content a Business writes or uploads (service descriptions, photos, messages) is that Business’s content; we help Businesses make it accessible but do not control it.
4.1 Target. We aim for WCAG 2.1 Level AA across the Service. We apply it first to the Customer pages listed in section 3.1, then to the Suds app.
4.2 Legal obligations. Where the Americans with Disabilities Act or another accessibility law applies to our Service, we treat accessibility as an ongoing duty: we fix barriers we learn about, put Customer tasks first, and offer another way to finish a task when a digital path does not work for you (section 10).
Measures in place today include:
These are the limits we know about today:
6.1 Dense staff screens. The schedule calendar, drag-and-drop boards, route maps, and photo-heavy screens in the Suds app are harder to use with a screen reader or keyboard alone than the Customer pages. Some drag actions do not yet have a keyboard alternative on every screen.
6.2 Maps. Maps (arrival tracking, routes, service areas) are visual. The address and arrival time are also shown as text, but map details are not fully available to screen readers.
6.3 Signatures and photos. Drawing a signature on a touch pad, taking a profile selfie, and capturing job photos need a pointer or camera. Where a signature is required, you can ask the Business or us for another way to sign.
6.4 Video and audio. Live camera views have no audio or captions. Call recordings, voicemails, and AI voice memos can have AI transcripts, but those transcripts can contain errors. Marketing videos may not all have captions yet.
6.5 Content from others. Photos, notes, messages, and AI-generated images that Businesses or Customers add may have no text description, and we cannot write one accurately for them.
6.6 Timed steps. Some card checks and one-time sign-in codes expire after a set time for security. If one runs out, you can start it again or ask for help under section 10.2.
6.7 Contrast in the dark theme. Some secondary text in the Suds app’s dark theme is lower in contrast than our target. We are raising it screen by screen.
6.8 Language. The Service is in English only.
6.9 Older screens. Rarely used settings and older tools may lag behind newer screens.
7.1 Embedded services. Some parts of the Service come from other companies, including the SudsPAY card checkout (provided by Whop), Google Maps, bank linking by Plaid, video calls by Zoom, and calendars for demo calls. Their accessibility depends partly on those providers. If one of them blocks you, tell us and we will help you finish the task another way when we can.
8.1 Browsers. The Service is built for current versions of Chrome, Safari, Firefox, and Edge on desktop and mobile. Older browsers may work less well.
8.2 Assistive technology. We check our work with keyboard-only use and with common assistive technology available to our team. Other combinations of devices, browsers, and assistive technology may behave differently.
9.1 Methods.
9.2 Audit status. We have not published a formal third-party WCAG conformance report. If we complete one, we will update this statement.
10.1 Report a problem. Email support@suds.com with the subject “Accessibility feedback.” If you can, include the page address, what you were trying to do, what went wrong, and the device, browser, and assistive technology you use.
10.2 Get help finishing a task. If something blocks you from booking, paying, changing an appointment, or managing your account, email support@suds.com with the subject “Accessibility accommodation” and tell us what you need. We can walk you through the steps by email or phone, or complete the task for you when that is appropriate and you authorize it.
10.3 Response times. We aim to reply within two business days and to give you a next step (a fix, a workaround, or a person to help) as soon as we can. Fixes to Customer pages come first.
10.4 Your information. We use what you send us only to answer your request and improve accessibility, as described in our Privacy Policy. You do not need to tell us about a disability to get help.
10.5 By mail. You can also write to us at Suds Software LLC, 10950 SW 5th St, STE 250, Beaverton, OR 97005.
11.1 Escalation. If our reply does not solve the problem, reply to it and ask for escalation. A different person at Suds will review it.
11.2 Other options. This statement does not limit any right you have under law, including the right to contact a government agency that enforces accessibility laws.
12.1 Updates. We review this statement as the Service changes and update the “Last updated” date at the top when we change it. This statement was last reviewed on October 24, 2026.
Suds Software LLC · 10950 SW 5th St, STE 250, Beaverton, OR 97005 · support@suds.com
See also our Privacy Policy, Terms of Service, SMS Terms, and Support.