Accessibility

Last updated: September 1, 2026

We want everyone to be able to plan a trip and find a dinner table with Eat, Slay, Love, including people who use a screen reader, larger text, or other assistive technology. This page says plainly what works today, what does not yet, and how to reach a person if something is in your way.

Our standard

We work toward the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA for this website and the equivalent platform guidance for the iOS and Android apps (Apple's Human Interface Guidelines for accessibility and Android's accessibility guidelines). We do not yet claim full conformance; this page is updated as things change.

What works today

Screen readers. Tabs, navigation, and the app's icon-only controls (back, close, send, save, delete, add photo, and similar) carry spoken labels for VoiceOver on iOS and TalkBack on Android, in the language the app is set to.
Text size. The app respects your device's text-size setting; no screen locks text to a fixed size.
Appearance. The app follows your device's light or dark appearance setting.
Text-first. Trip planning, itineraries, dinners, and chat are text, so they work without sound. Nothing important is conveyed by audio alone.

Known limitations

The Discover map. The map of nearby travelers and dinners is visual. The same people and dinners appear as cards you can swipe through beneath it, but a full list view for screen-reader users is still in progress.
Video clips. Short clips that travelers attach to places come from TikTok and Instagram and are played as-is; we cannot add captions to them.
AI-written itineraries are long-form text and can be verbose for screen-reader users; we are working on tighter headings and a per-day summary.
This website is checked with automated tools and by hand, but not yet by a third-party audit.

Tell us what is in your way

If any part of the app or this site is hard to use with assistive technology, or you need something in another format, email support@eatslay.love with "Accessibility" in the subject. Say which screen, which device, and what happened. A person reads every message, and we will reply and fix what we can in an upcoming app update.