Accessibility statement

EateryWebStudio wants eaterywebstudio.com to be usable by everyone, including people who use screen readers, keyboard navigation, magnification or other assistive technology.

Our commitment

We design and test this site with accessibility in mind from the start rather than bolting it on afterward, and we treat an accessibility problem as a bug to fix, not a feature request.

The standard we aim for

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. The site is built with the Americans with Disabilities Act (ADA) in mind. This statement describes our aim and our practice; it is not a certification or a legal opinion.

What we have done

• Semantic headings, landmarks and a skip link on every page.
• Every menu, drawer and panel can be opened and closed from the keyboard, with a visible close control and a visible focus ring.
• Color pairs chosen for readable contrast in both the light and dark themes.
• Motion that respects the reduced-motion setting on your device.
• Descriptive alternative text on meaningful images, and text content instead of images of text.
• An accessibility button in the lower left corner of every page for text size, contrast, link highlighting, readable fonts, text spacing and stopping motion, saved on your device only.

Known limitations

Some pages load third-party content, such as a booking calendar, a chat widget or a form, from other providers. We choose and configure these with care, but we do not control their code. If one of them causes a problem, tell us and we will offer another way to reach us.

Report a problem

If anything on this site is hard to use, email hello@eaterywebstudio.com with the page address and what happened. A person replies within one working day, during business hours (9 a.m. to 5 p.m. Central Time, Monday to Friday), and we will provide the information you need in another format while we fix it.

Websites we build for clients

Every restaurant website we build ships with its own accessibility statement and is built with the same WCAG 2.1 AA target in mind: readable contrast, keyboard access, alt text, real text menus and a way for guests to report a problem. Content that clients supply, such as photos and menu text, is published as confirmed by them.