Legal

Accessibility Statement

Last updated: July 28, 2026

Dakar Projects LLC (“Roddy HQ”) wants everyone to be able to use Roddy — both the website and dashboard you sign in to, and the phone line your customers call. This statement explains where we stand, what we know still needs work, and how to reach a human if something gets in your way.

1. Our commitment

Roddy is built so that a small business never misses a call. That promise only means something if everyone can actually use it — the business owner setting things up in the dashboard, and the person on the other end of the line trying to book an appointment. We want Roddy HQ to work for people who navigate by keyboard, use a screen reader, need larger text or higher contrast, are sensitive to motion, or are deaf, hard of hearing, or have a speech disability.

We’re a small team. We won’t pretend we’ve solved everything. But accessibility is something we design for as we build, not something we bolt on later, and we fix what we find.

2. Conformance status

We are working toward WCAG 2.1 Level AA (Web Content Accessibility Guidelines, published by the W3C). We consider roddyhq.com and the Roddy dashboard to be partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the site meets the standard, but some parts do not yet.

To be clear about what this statement is and isn’t:

• We have not commissioned a formal third-party accessibility audit, and we make no claim of certification by any organization.
• Our assessment is based on internal review during development — keyboard testing, browser and automated accessibility checks, and manual review of new pages and features.
• We know that internal review catches less than testing with real assistive-technology users does. Closing that gap is on our roadmap.

3. What we’ve done so far

Concrete measures already in place across the marketing site, the login flow, and the customer dashboard:

• Semantic HTML. Pages are built with real headings, lists, landmarks, buttons, and links — in a logical reading order — so screen readers and reader modes can make sense of the structure.
• Keyboard navigation. Interactive controls can be reached and operated with a keyboard alone, without a mouse or trackpad.
• Visible focus. We keep a clear focus outline on whatever element you’ve tabbed to, rather than removing it for looks.
• Contrast-conscious palette. Our colour system was chosen with text contrast in mind, and we don’t rely on colour alone to convey meaning — status and errors carry text or icons too.
• Reduced motion. We respect the prefers-reduced-motion setting in your operating system or browser; animations and transitions are reduced or stopped when you’ve asked for that.
• Alternative text. Meaningful images have text alternatives, and purely decorative graphics are hidden from screen readers so they don’t add noise.
• ARIA labels where they help. Icon-only buttons, toggles, and controls get accessible names, and we use ARIA to describe things native HTML can’t — but we prefer native elements first.
• Responsive layout and zoom. Pages reflow on small screens and support browser zoom and larger text sizes without content being cut off or trapped.
• Plain language. We try to write instructions, errors, and legal pages in words a normal person can read.

4. Known limitations

Here’s where we currently fall short. We’d rather tell you up front than let you discover it mid-task.

• The calendar grid. The dashboard calendar (day, week, and month views) is a dense, visually-oriented interface. It works with a keyboard, but reviewing and editing appointments there with a screen reader is harder than it should be. If this is a barrier for you, contact us — we can walk through alternatives, and improving this view is a priority.
• Data tables. Call logs and similar tables carry a lot of information per row, including sortable columns and expandable details. Header associations and sort announcements are not as complete as we want, so navigating them non-visually can be tedious.
• PDF call reports. Call transcripts and reports can be downloaded as PDFs. Those PDFs are generated in the browser and are not reliably tagged for accessibility — reading order and structure may be poor with a screen reader. The same content is available as on-screen HTML in the dashboard, which is the accessible route, and we’ll supply a plain-text version on request.
• Motion on the marketing site. Our home page includes a scrolling marquee and some decorative motion. It pauses when you’ve set prefers-reduced-motion, but it is still motion by default, and we haven’t yet added a visible on-page control to stop it.
• Third-party and embedded content. Some parts of the experience are provided by other companies — sign-in, payment and payout screens, calendar authorization from Google and Microsoft, and any embedded content we don’t author. We choose vendors carefully, but we don’t control their code or their accessibility, and we can’t promise those screens meet WCAG 2.1 AA.
• The chat widget on customer websites. Businesses can embed the Roddy chat widget on their own sites. We’re improving its keyboard and screen-reader behaviour, and how it appears depends partly on the host site’s own code.
• Older content. Occasionally a page or an image caption slips through without a proper text alternative. If you find one, tell us and we’ll fix it.

5. Using the phone service itself

Roddy is a voice product, so accessibility isn’t just about our website — it’s about the call. If speaking or hearing on the phone is difficult for you, here’s what’s available.

Relay services and 711

Relay calls — 711 relay, TTY relay, speech-to-speech relay, captioned telephone, and video relay — reach a business using Roddy the same way any other phone call does, and Roddy will answer.

An honest limitation: Roddy listens for a pause to know when it’s your turn, and it ends a call that stays silent for a while. Relay and captioning add a delay between turns, so on a relay call Roddy may speak too soon, or may end the call before you’ve finished typing. We have not yet finished testing Roddy against the full range of relay services, and we won’t claim it works well until we have. If you say “hold on” Roddy will wait longer, and asking for a person will get you a message taken or a transfer — but if relay is how you call, the text options below will be the smoother path today.

We’re working on this, and it is the accessibility issue we most want to hear about. If a relay call to a business using Roddy didn’t go well, tell us the number you dialled and roughly when, and we’ll trace it.

Text instead of talking

• The chat widget. Many businesses using Roddy also run the Roddy chat widget on their website. It’s a fully text-based way to ask the same questions and request the same appointments, with no phone call at all. If you’d rather not speak, look for the chat button on the business’s site.
• Transcripts. Every call Roddy handles is transcribed to text. We do not store audio recordings of calls — only the written transcript, a summary, and call details. Business owners can read the full transcript of any call in their dashboard rather than listening back to audio.
• Email follow-up. Roddy can take a message and email it to the business, and can send written confirmations for bookings, so an interaction doesn’t have to end on the phone.

You can always ask for a person

A caller is never locked into talking to the AI. At any point in a call you can say something like “let me talk to a person,” “transfer me,” or “I need a human,” and Roddy will try to transfer you to the business, or take a message so a person can call or email you back. You do not have to phrase it in any particular way, and you don’t have to explain why.

Two honest caveats: whether a live person is available depends on the individual business and its hours, and speech recognition can misunderstand people — including people with speech disabilities, strong accents, or atypical speech patterns. If Roddy repeatedly mishears you, asking for a human or using the chat widget is the fastest route, and we’d genuinely like to hear about it so we can improve.

Roddy is not for emergencies. It cannot reach emergency services. In an emergency, call 911 — including via 711 relay or by texting 911 where that service is available in your area.

6. Feedback and getting help

If you hit a barrier anywhere in Roddy — the website, the dashboard, the chat widget, or a phone call — please tell us. Reports from real users are the single most useful thing we get, and you don’t need to know any technical terms to send one.

• Email: admin@dakarprojects.com
• Phone: (844) 318-9207 — reachable via 711 relay
• Mail:by email or phone using the details above

It helps if you can include the page or phone number involved, what you were trying to do, and what assistive technology, browser, or device you were using — but send it even if you can’t.

Our response target: we aim to reply within 5 business days. If a fix will take longer than that, we’ll tell you what we’re doing and roughly when to expect it, rather than going quiet.

Alternative formats. If any information we publish isn’t usable for you, ask and we’ll provide it another way at no charge — plain text or large-print versions of this page and our other legal pages, call transcripts and reports as accessible text instead of PDF, or a walk-through by phone or email instead of on-screen instructions.

7. If we don’t get it right

Please come to us first — we can usually fix things faster than any formal process. Email admin@dakarprojects.com with “Accessibility” in the subject line and we’ll treat it as a priority.

If you’ve raised something with us and you’re not satisfied with our response, say so directly and we’ll escalate it internally for a second look. You also always retain the right to seek outside help. In the United States, the Department of Justice runs an ADA Information Line at 800-514-0301 (TTY 800-514-0383), and complaints about telephone relay services can be raised with the Federal Communications Commission. We’d rather resolve it with you, but we’re not going to pretend those options don’t exist.

8. Approval and review

This statement was prepared by Dakar Projects LLC and reflects a self-assessment of roddyhq.com, callroddy.com, and the Roddy dashboard against WCAG 2.1 Level AA. It has not been evaluated or endorsed by an outside auditor.

Approved by Dakar Projects LLC on July 28, 2026. We review this statement, and re-check the site against it, at least once a year, and whenever we ship a significant change. Next scheduled review: July 28, 2026.

As we add features — including things we’ve planned but not built yet, such as text message confirmations — we’ll assess them for accessibility and update this page rather than leaving it stale.