Accessibility

Updated July 2026

Where this stands

This is an honest statement of what the site does today, not a claim of WCAG conformance. It has not been formally audited against any standard. Below is what we have checked ourselves and what we know is limited.

What works

Filters, price toggles, and the custom dropdowns (borough, cuisine, grade, rating, sort, and the rest) are all operable from the keyboard, and each shows a visible focus outline when tabbed to. The results list, the mobile bottom sheet, and its drag handle can also be operated by keyboard: the handle responds to Enter or Space to cycle the sheet between peek, half, and full height, and it is a full tap target on touch screens too.

The page markup uses semantic elements, fieldsets and legends for grouped filters, headings for restaurant names and section titles, buttons for actions, and landmark regions for the map, the results list, and the detail panel, rather than generic clickable divs.

Animation respects your system's reduced-motion setting: sheet transitions, dropdown fades, and the loading skeleton's pulse are all suppressed when prefers-reduced-motion is set.

The one photo on a restaurant's detail panel is marked decorative (empty alt text), since the restaurant's name is already presented as a heading right next to it, so nothing is lost to a screen reader by skipping the image itself.

Known limitations

The map is inherently a visual, spatial interface. It is not a substitute for the data itself. Every restaurant on the map is also in the results list, in the same order, with the same filters applied, and the list is the accessible equivalent path to the same information for anyone who cannot or would rather not use the map directly.

This has not been tested with a screen reader end to end, and there are almost certainly rough edges we have not found. If something does not work for you, we want to know about it.

Report a problem

Email eat@shedua.com with what you were trying to do and what happened. Specifics help a lot, a page, a control, and the assistive technology or browser you were using.