Built to be usable by everyone.

SERVD is built to be usable by everyone — including people who use screen readers, navigate by keyboard, rely on captions, or have low vision, low motor function, or cognitive differences.

Our target is conformance with Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. When we fall short — and we will, in places — we want to know about it so we can fix it.

Across the Platform:

• Keyboard navigation for every interactive element. Tab order follows the visual reading order.
• Semantic HTML — proper headings, landmarks, form labels, and ARIA roles where native HTML can’t do the job alone.
• Color contrast verified at 4.5:1 minimum for body text and 3:1 for large text, against our cream background.
• Visible focus rings on every interactive element. We don’t rely on hover.
• Alt text on every meaningful image. Photos of chefs, menus, and partners carry descriptions that work without sight.
• Reduced motion respected via prefers-reduced-motion. The hero video, the scroll-tied wordmark, and the counter animations all reduce or disable themselves when your system asks for less motion.
• Form validation announces errors via association with the field, scrolls to the first error, and preserves your input so you don’t have to re-type.
• Heading hierarchy — every page has a single H1 and a sensible H2/H3 structure for screen-reader users who navigate by headings.

We’re actively improving in the following areas. If any of these affect your use of the Platform, please tell us — we prioritize based on reports.

• Screen reader testing across NVDA, JAWS, and VoiceOver on every shipped surface. We test on VoiceOver today; NVDA and JAWS coverage is expanding.
• Captions and transcripts for the homepage hero video and any chef-stories video content we publish.
• Speech-to-text for diner-to-chef messaging.
• Plain-language menu descriptions alongside chefs’ editorial descriptions, for diners with cognitive or reading differences.

SERVD is tested against the latest two versions of:

• Chrome (desktop and Android)
• Safari (desktop and iOS)
• Firefox (desktop)
• Edge (desktop)

With these assistive technologies:

• VoiceOver (macOS and iOS)
• NVDA (Windows)
• JAWS (Windows)
• Browser zoom up to 200%
• System dark mode (the Platform respects your preference)

If you encounter a barrier on the Platform, please write us at a11y@servdchefs.com with:

• The page URL where it happened.
• What you were trying to do.
• What happened instead.
• Your browser, operating system, and any assistive technology you were using.

Our response-time goal is 5 business days for an acknowledgement and a fix ETA, faster for issues that block access to a core flow (sign-in, booking, payment, support).

With your permission, we credit reporters publicly when a fix ships. If you’d rather stay anonymous, just say so and we’ll log the fix without your name.

We’re also happy to hear from you about:

• Patterns we use that work well for you (so we don’t accidentally regress them).
• Features that would meaningfully expand who can use SERVD.
• Specific chefs or menus we should help present in a more accessible way.

Accessibility is a moving target. Every release should be better than the last one. The reports we get from real users are what move us along the curve fastest.