Accessibility
Last updated 2 October 2026
The standard we aim for
We want Curbadeed to work for everyone, including people who use a screen reader, a keyboard instead of a mouse, zoom, or reduced-motion settings. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, on the public pages and in the signed-in app.
What we do
- Check the public pages and the app with automated accessibility tools before each release, on phone and desktop sizes.
- Make every link, button and form field reachable by keyboard, with a visible focus outline. Rows that scroll sideways can be scrolled by keyboard too.
- Label every form field and checkbox, and say what went wrong in words, not only in color.
- Turn animations down when your device asks for reduced motion.
- Keep text readable when zoomed, without sideways scrolling of the page.
No overlays
We don't use accessibility overlay widgets. We fix the pages themselves.
Known limits
- The map and the 3D skyline view are visual. Everything on them is also in the Properties list, which works with a keyboard and a screen reader.
- Aerial photos of a property are decorative; the address, the city's record and the score are always given as text.
- Printed letters are as accessible as the template you choose; you can edit the text before printing.
Tell us about a barrier
If something in Curbadeed is hard or impossible for you to use, email curbadeed@wrinkledot.com with the page and what happened. We reply within 5 business days and will help you get the information another way while we fix it.