Menu Design
Photo vs No Photo on a Chinese Restaurant Menu
Photos can help diners order unfamiliar Chinese dishes, but a photo-heavy menu can also look cluttered, cheap, or misleading.
When photos help
| Use photos for | Reason |
|---|---|
| Unfamiliar regional dishes | A photo reduces uncertainty when the name is not self-explanatory. |
| House specialties | Visual emphasis helps direct demand. |
| Dim sum and bakery items | Shape and wrapper type matter. |
| Hot pot ingredients | Cuts, portions, and platters are visual. |
| Online menus | Photos can improve conversion if accurate and fast-loading. |
On long menu pages, WCAG expects a way to bypass repeated blocks such as navigation, which is why skip links and clear main-content landmarks matter. ADA guidance treats accessible digital communication as part of serving the public effectively, not just as a design preference. WCAG expects link purpose to be clear from the link text or surrounding context, so labels like "Lunch menu PDF" are stronger than "click here." WCAG 2.2 sets a 4.5:1 contrast minimum for normal text and 3:1 for large text.
When photos hurt
| Problem | Why it hurts |
|---|---|
| Too many photos | The menu becomes harder to scan. |
| Inaccurate photos | Trust falls when the dish does not match. |
| Low-quality lighting | Food looks greasy, dull, or old. |
| Stock photos | The restaurant loses credibility. |
| Slow mobile load | QR menu use becomes frustrating. |
Practical rule
Use fewer, better photos. Photograph the dishes the restaurant wants diners to order, and keep the rest of the menu clean, readable, and text-based.