Legal
Accessibility
Statement.
Our target, what's already in place, what still needs work, and how to reach us.
Last updated: July 30, 2026
- Our commitment
- Conformance target
- What we've done
- Known limitations
- Browser & assistive technology compatibility
- Feedback & reporting an issue
- Enforcement procedures
- Changes to this statement
Our commitment
dmly builds an AI-powered Instagram employee for businesses, and we want it to be usable by as many people as possible — including business owners and their customers who use assistive technology such as screen readers, screen magnifiers, voice control, or keyboard-only navigation. We're actively working to make our marketing site and dashboard conform to recognized accessibility standards, and to fix issues as we find or are told about them.
Conformance target
Our target is WCAG 2.1 Level AA, the standard referenced by most accessibility laws, including the ADA in the United States. We treat this as an ongoing target we measure ourselves against, not a certification — dmly is a small, actively-changing product, and we haven't commissioned a third-party audit. Where we know we fall short, we say so below rather than claim full conformance.
What we've done
- Every form field on the site (sign-up, login, checkout, contact) has a visible, programmatically-associated label — not just a placeholder.
- Text and UI colors are checked against WCAG AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI components); we periodically re-run automated contrast audits as the design evolves.
- Every page has a "skip to main content" link for keyboard users, so you're not forced to tab through the header and navigation on every page.
- The mobile navigation menu announces its open/closed state to screen readers and moves focus sensibly when opened and closed.
- Keyboard focus is visible on interactive elements — we don't suppress the focus outline without providing a replacement.
- Decorative images, icons, and animations are hidden from assistive technology (
aria-hidden) so they don't clutter the experience for screen reader users; functional icons (e.g. the "back to top" button) have text alternatives. - The site respects
prefers-reduced-motionfor people sensitive to animation.
Known limitations
We haven't reached full conformance yet. Known gaps we're tracking include:
- Some of the more elaborate scroll-driven and canvas-based visuals on the marketing site (the hero contour map, the orbiting integrations diagram) are primarily decorative but haven't each been individually reviewed for equivalent text alternatives.
- The product dashboard — the flow builder, analytics, and admin views — is a complex, drag-and-drop interface and has not yet had the same level of accessibility review as the marketing site. Keyboard-only and screen-reader use of the flow builder in particular is limited today.
- Some third-party embedded components (e.g. payment and OAuth flows hosted by our providers) are outside our direct control; their accessibility depends on the provider.
We're addressing these in order of impact, starting with anything that blocks a customer from completing a core task like signing up, logging in, or contacting us.
Browser & assistive technology compatibility
dmly is built to work with recent versions of major browsers (Chrome, Safari, Firefox, Edge) on desktop and mobile, and is tested informally with common screen readers such as VoiceOver and NVDA. It relies on standard HTML, CSS, and JavaScript rather than plugins.
Feedback & reporting an issue
If you use assistive technology and run into something on dmly that doesn't work for you — a page you can't navigate, text you can't read, a control you can't operate — please tell us. We treat these reports seriously and prioritize fixes.
Email [email protected] with a description of the issue, the page or feature involved, and the browser/assistive technology you were using. We aim to acknowledge reports within 3 business days and to give you a timeline for a fix. For everything else, reach out here.
Enforcement procedures
If you're not satisfied with our response, or the issue hasn't been resolved in a reasonable time, you're welcome to escalate through whatever accessibility complaint or enforcement process is available in your jurisdiction. We'd genuinely rather hear from you directly first, so we can actually fix the problem.
Changes to this statement
As we fix known issues and review more of the product, we'll update this page and the date above. This statement reflects a good-faith, ongoing effort rather than a one-time certification.