Accessibility Statement
- Version:
- 2026-04-19.1
- Last reviewed:
- April 19, 2026
LetsCrawl is committed to making our apps and website usable by as many people as possible. This statement describes the accessibility standards we target, the limitations we are aware of, and how to reach us if something is not working for you.
Our commitment
We believe nightlife should be easy to plan and enjoy for everyone, including people who use assistive technology, rely on keyboard navigation, or need extra contrast, larger type, or reduced motion. Accessibility is a first-class concern on the engineering roadmap, not an afterthought, and we iterate on it as we ship new features.
We design and test against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and follow the equivalent platform guidance on iOS and Android so that screen readers, switch controls, voice control, and Dynamic Type continue to work.
Standards we target
Our target is WCAG 2.1 Level AA. In practice that means we verify color contrast, focus order, heading structure, form labels, accessible names for interactive elements, motion preferences, and support for keyboard-only and screen-reader navigation on every release.
On mobile, we honour the platform settings for VoiceOver, TalkBack, Dynamic Type, Bold Text, Reduce Motion, and high-contrast modes. Reported issues are triaged on the same track as security and privacy bugs.
Known limitations
We are aware of, and actively working on, the following gaps: interactive maps do not yet expose a fully equivalent list-based view for screen-reader users; some third-party venue images are missing alternative text until a partner feed supplies it; and a small number of older marketing illustrations still use text-in-image that cannot be resized without loss.
If you run into a barrier that is not listed here, please let us know using the contact details below so we can prioritise it.
How to report an issue
If you have trouble using any part of LetsCrawl, email us at [email protected]. Please include the page or screen, the device and assistive technology you are using, and a short description of what went wrong. We aim to respond within five business days and to propose a fix or workaround in our reply.
You can also ask us to provide information from our site in an alternative, accessible format (for example, plain text) at no extra cost.
Last reviewed
This statement is reviewed on every release and whenever we make a material change to the app or website. The date at the top of this page is stamped automatically from the deployment that served it.