Accessibility
Last updated 18 October 2026
Our aim
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every page of this site, in all four languages: English, Hindi, Spanish and French.
We are not there yet in every place. This page sets out what we have checked, what still falls short, what we have not tested, and how to tell us about a problem.
What helps
Pause. The home page opens with an animation of a working day. It plays once, then stops. Pause is the first control inside it. It stops all movement on the page, and Play starts it again. Anywhere else on the site, movement stops by itself within five seconds.
Reduced motion. If your phone or computer is set to reduce motion, the site follows that setting. The home page shows one still picture instead of the animation, the day is written out as a list, and scrolling is not smoothed.
Text size. Choose Standard, Large or Larger from the Aa button at the top of the page (Text Size and Colours). Larger makes text 137.5% of its standard size. On a phone, the same choices are in Menu. Browser zoom works too.
Colours. The same menu has a light look and a dark look, or Auto, which matches your phone or computer. We checked text contrast in both looks.
Keyboard. Everything we tested works with a keyboard alone, including the menus, the language choice, the chat demo and the contact form. Each page starts with a Skip to Content link. Escape closes a menu and takes you back to the button that opened it. Whatever has keyboard focus is shown with a ring.
Screen readers. Each page has a title, one main heading, headings in order, and named areas such as the main navigation and the footer. Every button and link has a name. Each page says which language it is in, so a screen reader can switch voice. On the contact form, each problem names its field, and focus moves to the first one.
Buttons and links are at least 24 by 24 pixels, or have enough space around them.
How we check
On 18 October 2026 we made our first check of the site against our accessibility checklist, which follows WCAG 2.2 level AA. It covers: moving content and Pause; the reduced-motion setting; using the site by keyboard; where focus goes and whether you can see it; messages a screen reader reads out, such as replies in the chat demo; text contrast, at several times of day in the home page's animation and in both looks; pages 320 pixels wide with Larger text, in all four languages; larger text and 200% zoom; the size of buttons and links; errors and labels on the contact form; and headings.
In WCAG terms, the checklist covers 1.3.1, 1.4.3, 1.4.4, 1.4.10, 2.1.1, 2.2.2, 2.4.3, 2.4.6, 2.4.7, 2.4.11, 2.5.8, 3.3.1, 3.3.2 and 4.1.3, plus our own rule on reduced motion. It does not yet cover every WCAG 2.2 AA criterion.
We ran it in Google Chrome on Windows 10, at desktop and phone sizes, at sizes that match 200% and 400% zoom, and with Larger text. We measured contrast from what was drawn on screen.
We also tested with the NVDA screen reader, version 2026.2, and Google Chrome on Windows, using only the keyboard, on the home page, What We Build, Talk to Us and the Hindi home page. We kept a log of everything NVDA said and read it back.
The axe automated checker found no problems on the home page, What We Build and Talk to Us, in English and Hindi. Our automated tests also check the main pages at phone and desktop sizes before each release.
We repeat the checklist at each release and update this page after each full check.
Not tested yet
This first check is not complete. We have not yet tested with VoiceOver on iPhone with Safari, or with NVDA and Firefox. We have not tested other screen readers, such as JAWS, or TalkBack on Android, or browsers other than Chrome.
Our test computer had no Hindi voice, so the Hindi pages were read with an English voice. We have not yet heard them read by a Hindi voice.
Booking a call uses a calendar from Cal.com, another company. It was not part of our check. If it does not work for you, email us instead.
Known limits
These are problems we found and have not fixed yet.
Pause at sunset and sunrise. While the sky in the home page's animation passes sunset, the Pause button is hard to read for about two seconds, and for a moment at sunrise. On a phone, the Pause icon is faint at the same moments. We plan to put Pause on a fixed dark background. If your device is set to reduce motion, the animation does not play at all.
Some white text on red. The hint in the chat demo, and step numbers when they light up, have a little less contrast than WCAG asks for: 4.09 to 1, where 4.5 to 1 is needed. We plan to use a darker red.
Focus at high zoom and on wide screens. At 400% zoom on the home page, one Start Your Prototype link takes focus while it is off screen, so you cannot see it. A few links and buttons on the home page and What We Build are still fading in when they take focus, so for a moment they look faint. On a wide screen, the Chat, Back-office and Custom buttons on the home page sit partly under the top bar when they take focus.
Headings that appear late. On the home page and What We Build, a few headings, the chat demo and its “Behind the chat” panel reach screen readers only once that part of the page has been drawn. If you list the headings as soon as the page opens, up to three may be missing. Scrolling through the page once brings them in. We saw this in Chrome and have not yet checked how screen readers handle it.
The phone in the home page's animation. It is one picture with a short text description, so a screen reader cannot go through the parts inside it one by one. The day it shows is written out as a list below it.
The spam check on our contact form. It is run by Cloudflare (Turnstile), and we have not tested it with a screen reader. If it asks you to do something you can't, email hello@dubsenterprises.com instead.
Smaller points. The heading “We build the parts of your business that repeat, so they run without you.” is read without the space after the comma. On the French home page, 320 pixels wide with Larger text, the arrow at the end of each “Voir comment ça marche” link is cut off, and one heading breaks inside a word without a hyphen. On What We Build, at the same width with Larger text, the first line of each example notification is cut short with three dots; these are decorative examples.
Changed since our check
Since 18 October 2026 we have fixed the problems below. We have checked the fixes with automated tests in Chrome, but not yet with a screen reader.
In the chat demo, a screen reader heard only the start of each reply before the next choice was read out. Now each reply is read once, in full, and your own choice and “typing” are no longer read back. In the café conversation, the menu is read with pauses between items.
With a keyboard, each reply in the chat demo is now read as part of the next button you land on. If your screen reader is set not to read descriptions, you may miss it. Reading down the conversation still gives you every line.
With the phone menu open, the keyboard could move to the page hidden behind it. Now the keyboard and screen readers stay in the menu and the top bar until you close it.
What We Build read out its example order by itself when the page opened. Now it says nothing until you press Run It, then reads the result once, at the end.
Under Pause, the chat demo's first messages still slid in. Now they simply appear.
Smaller fixes: the home page's main heading is read with a space between its two sentences; the language button is read as “Language: EN”; on the Hindi, Spanish and French pages, the chat demo gives days and times in the page's language, and names from the examples are marked with their own language; the navigation areas are named in each page's language; and the contact form reads out its step count only when the step changes, and marks a missing time choice as a problem only after you try to go on.
Tell us about a problem
If something on this site does not work for you, please tell us. Email hello@dubsenterprises.com with “Accessibility” in the subject, or write to us through Talk to Us.
You can also message us on WhatsApp, from the Chat on WhatsApp link at the bottom of every page.
It helps to know the page, what you were trying to do, and what you use, such as your screen reader, browser and device.
We will reply and tell you what we will fix and when. If you need something on this site in another form, say so and we will send it to you by email.
About this statement
This statement is based on our check of 18 October 2026 and the fixes made since. We update it after each full check.