Accessibility

What we build to

This site targets the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and we are working toward WCAG 2.2 AA.

Last reviewed

September 30, 2026

Reviewed by

Automated testing (axe-core) and a full keyboard walk-through, on desktop and phone

What that means here

• The full menu is real text on a web page, not a picture or a PDF. A screen reader can read every dish and description, and you can search it.
• Everything works with a keyboard alone: press Tab to move and Enter to activate. The focus outline is always visible, and a “Skip to content” link comes first.
• Every photograph has a written description, or is marked as decorative so a screen reader passes over it.
• Text on the cream background meets a contrast ratio of at least 4.5:1.
• Headings follow a real order, so you can jump between sections rather than scrolling.
• On touch screens, every standalone link and button is at least 44 pixels tall. Links inside a sentence are exempt and stay the size of the text.
• Text can be enlarged to 160% with the accessibility menu and every page still fits a phone screen, with nothing cut off.
• The video at the top of the home page is silent and decorative. It has a Pause button, stays paused if your device asks for reduced motion, and stops when you choose “Stop Animations” in the accessibility menu.
• The page language is declared and every page has its own title.

The accessibility menu

The round blue button in the bottom-left corner of every page opens an accessibility menu. On a phone it sits just above the row of buttons along the bottom of the screen. It can make text larger, switch to a font designed for dyslexia, raise the contrast, turn the page to greyscale, stop animations, enlarge the cursor, and more.

• With a keyboard: press Tab until the button is highlighted (it is the last stop on every page), then Enter or Space to open the menu. Tab moves through its options and stays inside it; Escape closes it and puts you back on the button.
• Your choices carry from page to page and are still there next time you visit.
• They are saved in your browser, on your own device. The menu sets no cookies (it would use one only if your browser blocked that storage) and sends nothing about you or your settings anywhere. Its code, and the dyslexia font and translations when you choose them, load from the jsDelivr network.
• The “Accessibility Statement” link at the foot of the menu brings you to this page.

The menu is a convenience added on top of a site that is built to be accessible on its own. You do not need it to use anything here, and it is not a substitute for the work described above.

Still being worked on

• Ordering and delivery happen on other companies’ sites: orderfood.express for pickup, and GrubHub, Uber Eats and DoorDash for delivery. We do not control how those are built. If one of them stops you placing an order, call us on (650) 873-8341 and we will take it over the phone. Our number is on every page, in the footer and, on phones, in the bar along the bottom of the screen.
• The map on the Visit page is Google’s. The address and a directions link are always written out beside it, so you never need the map itself.
• The site has been checked with automated tools and by keyboard. It has not yet been tested by a person using a screen reader; that review is still to come.

Tell us about a barrier

If any part of this site is hard to use, we want to hear about it and we will fix it. Call, email, or tell us in person at 146 Hazelwood Dr., South San Francisco, CA 94080.

Email goes to whiteelephantssf@gmail.com, the restaurant’s general address; there is no separate accessibility inbox.

We aim to meet this standard and we keep testing against it, but we cannot promise a site is free of every problem. Contact details are on the Visit page.