Accessibility statement

We want the Dictate Safe website to work for people who browse in different ways, including with a keyboard, a screen reader, a magnifier or reduced motion. This statement says what we aim for, what we have checked, where the website falls short, and how to tell us about a barrier.

1. What this statement covers

It covers the public pages of the Website at dictatesafe.com: the home page, the features and use case pages, pricing, the blog, the help centre, the legal pages and the sign-in page.

It does not cover the account area that you see after you sign in, the pages that other companies run for us (the payment window, and the Google and GitHub sign-in pages), or the Dictate Safe App.

2. The standard we aim for

We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, published by the World Wide Web Consortium. That is our aim. We do not claim that the Website meets it.

3. What we have checked, and by whom

We checked the public pages between 4 and 6 October 2026, and fixed the problems we found. Our own team made the checks, using a browser, the keyboard and automated scripts. No independent accessibility audit has been done. On the pages we checked:

• Each page says in its code that it is written in English, so a screen reader uses the right pronunciation.
• A "Skip to content" link is the first thing the Tab key reaches, and the main content of each page is marked.
• You can reach the links and buttons with the keyboard. The menus open with Enter or the Down arrow and close with Escape. The place where you are on the page is marked with a clear outline.
• Pictures have a text description or are marked as decoration. Each animated demonstration has a short written description and a pause button you can reach with the keyboard.
• If your device is set to reduce motion, the site's animations stop.
• We measured the contrast of text against the page background and made normal text meet the ratio of 4.5 to 1 that the standard asks for. Text inside pictures of the App keeps the App's own colours.
• The pages fit a screen 320 pixels wide without sideways scrolling.
• The cookie box is a labelled dialog that you can use with the keyboard. The help centre's search tells a screen reader how many results match.
• In a high contrast mode, buttons, switches, icons and the logo stay visible. We checked this by emulating forced colours in Chrome.

4. Where the Website falls short

• We have not yet tested the Website from start to finish with screen reader programs.
• We checked high contrast colours in Chrome on a Mac, not on Windows itself, and we have not looked at the use case pages in that mode.
• A screen reader hears one sentence about each animated demonstration. There is no step by step description beyond that sentence and the page text around it.
• We have not checked the account area, and the App has not been audited.
• The chat window and the voice call with our AI agent were added after our checks, and we have not checked them with assistive technology. The chat window works as text, and a call shows captions of what is said. If either stops you, write to us and we will help you another way.

If one of these stops you doing something, tell us and we will help you another way.

5. Telling us about a barrier

If something on the Website is hard or impossible for you to use, email support@dictatesafe.com or use the Contact page at https://dictatesafe.com/contact. Tell us the page, what you were trying to do and what happened. You may add your browser and any assistive technology you use, but you do not have to.

We reply within a reasonable time. Where we can fix the problem, we will, and we will tell you when it is done. Where a fix takes longer, we will tell you what we plan to do and get you what you needed another way, for example by sending you the content of a page as plain text by email. We do not promise a date for every fix.

6. If you are not satisfied

If you are in the European Union and you are not satisfied with our reply, you can contact the authority in your country that is responsible for enforcing accessibility rules.

7. Date of the last review

We last checked the Website on 6 October 2026. We prepared this version of the statement on 16 October 2026 from the results of that check. When we fix a problem listed in section 4 or find a new one, we update this page and the version and date above.

Document history