Real headings and labels.
Every page starts with real headings, landmarks, links, buttons, form labels and a sensible reading order. Visual effects come last.
Accessibility
This page covers what our apps and this website do for people who use a screen reader, large text or a keyboard.
How it works
You can use our apps and this site with a screen reader, large text or only a keyboard. The six steps below are what we check before anything goes out.
How we build
Every page starts with real headings, landmarks, links, buttons, form labels and a sensible reading order. Visual effects come last.
Everything you can do with a mouse, you can do with a keyboard. You can always see where you are, and Tab moves in an order that makes sense.
We listen to important steps with a screen reader: the spoken labels, the errors in a form, where focus goes in a dialog, status messages and the page structure.
If you turn on Reduce Motion, you keep exactly the same content and controls. You never need to see an animation to understand a page.
We do not use ad tracking, fingerprinting or tracking across websites, and our privacy pages say exactly what is switched on.
If a label is unclear or a step is hard to use, tell us. That is how we learn what to change.
Accessibility statement
Dakkak Labs aims to meet WCAG 2.2 level AA across this website: text contrast of at least 4.5 to 1, touch targets of at least 44 points, and no meaning shown by colour alone. The site includes keyboard navigation and display settings for text size, contrast, motion, and transparency. Your choices are saved on your device. You can turn on Reduce motion in Accessibility settings to make animations static.
Last reviewed November 2, 2026.
If something gets in your way, email [email protected] and tell us what you were trying to do. We'll treat it as a bug.