Accessibility and inclusion

What we're building toward

Dripbase is meant to work for someone on a phone, on a slow connection, using a screen reader — not as an edge case, but as the actual reader we're designing for. A lot of Dripbase happens outside, on a driveway, glancing at a screen in direct sun while a detailer is en route. That's the bar.

Concretely, what we hold ourselves to on every page: one heading per page, headings that go in order rather than skipping levels, link text that says where it goes instead of "click here," alt text that describes what an image actually shows, and color contrast that still reads outdoors. Any emoji is either hidden from a screen reader or given a real label, not left to be read aloud as a word.

What we don't claim

No one has run a third-party audit of Dripbase against an accessibility standard, so we're not going to tell you it meets one. Claiming a conformance level nobody checked would be exactly the kind of promise this help center exists to avoid. What follows instead is what we've actually found, good and bad.

Where we know we've fallen short

Two specific gaps are open and tracked right now, not hidden:

• On this site, there's a known issue where heading levels skip on at least one page, and at least one form doesn't tie its error message to the field it belongs to — which matters a lot if you're using a screen reader, since both make it harder to tell what's wrong or where you are.
• Our internal staff console — the tool our own ops team uses, not something you'd ever see as a customer — has unlabeled buttons, errors that don't get announced, and dialogs that aren't declared as dialogs to assistive technology. We're naming it here anyway, because the same standard applies whether or not a customer is the one looking at the screen.

Both are logged as open work, not settled for. We'd rather point at the exact problem than describe the product as further along than it is.

Language

Dripbase is English-only right now. There's no translation of the site or the app into other languages yet.

If something doesn't work for you

If a screen reader can't get through a page, if contrast is too low to read outside, or if anything else here isn't actually true when you try it, we want to know. We have to be honest that Dripbase doesn't yet have a dedicated, in-product way to send that report — see Reporting a problem with a job for the larger version of that gap. Until a real channel exists, the most useful thing we can do here is not overstate what's already working.