Accessibility

Our commitment

Bakes & Brews is a neighbourhood café, and a neighbourhood means everyone. Our goal is for this website, bakesandbrews.shop, to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That covers:

• the home page, including the “Not yet.” ordering note and the “Hear it first” form,
• the Community Shelf page,
• our privacy policy, and
• this page.

We’re building the Community Shelf app at shelf.bakesandbrews.shop to the same standard, and we’ll check it the same way before it opens.

What we’ve built in

• A “Skip to content” link, clear headings and named page regions, so you can jump to what you need.
• Everything works with a keyboard, and the item you’re on always has a visible outline.
• Text and controls meet the colour contrast guidelines, and buttons and links are at least 44 pixels tall, so they’re easy to tap.
• Every form field has a label. Errors say what went wrong and how to fix it, and screen readers announce them.
• The page reflows to one column when you zoom in. On short or zoomed screens, the header and the bottom bar stop following you, so they never cover what you’re reading.
• The site follows your device settings for reduced motion, more contrast and high-contrast colours.
• Pictures that carry meaning have text alternatives. Decorative ones are hidden from screen readers.

How we test

We check every page, and every state a page can be in: the ordering note, form errors, the thank-you card, the mobile bottom bar and the map.

Automated checks

We run axe, a widely used accessibility checker, on every page and state.

Keyboard only

We go through each page with Tab, Shift+Tab, Enter, Space and Escape. We check that the order makes sense and that the item you’re on is always visible, never hidden.

Screen reader checks

We check what screen readers announce: page titles, headings, landmarks, the names of links, buttons and fields, and messages like errors and confirmations.

Zoom and reflow

We check the pages at 200% and 400% zoom, at 320 pixels wide, on phones held both ways, and with text set to twice its usual size.

High contrast

We check Windows contrast themes (forced colours) and the “increase contrast” setting.

Known limitations

We’d rather tell you than have you find out. These are the parts we know aren’t perfect yet.

• The map on our home page comes from Google. We can’t change how its controls work with a keyboard or screen reader. Our address is written out next to it, and the “Get directions” link opens Google Maps in a new tab.
• Instagram, WhatsApp and Google Maps are other companies’ sites. When you follow a link to them, their own accessibility applies.
• The “Hear it first” form can’t yet confirm that your details reached our list. The thank-you card shows once your details are sent, but the form can’t tell if our Google Sheet had a problem saving them. If you don’t hear from us when we open, call us and we’ll add you by hand.
• Online ordering isn’t open yet. The ordering buttons show a short note instead. You can always call us.
• We haven’t tested every combination. We test mostly in Chrome and Edge, and we haven’t yet tried every browser, screen reader and phone. If yours gives you trouble, please tell us.

Get help or report a barrier

If anything on this website is hard to use, or you need the information in a different way, we want to know.

• Call us at (925) 301-8384.
• Message us on Instagram at @bakes.brews.
• Once we open, ask anyone at our counter at 5019 Lone Tree Way, Ste B, Antioch, CA 94531.
• Email us at support.bakesnbrews@gmail.com.

It helps if you tell us which page you were on, what you were trying to do and what got in the way. If you use a screen reader, magnifier or other tool, you can tell us which one. You don’t have to.

What happens next

A real person at the café will get back to you as soon as we can. While we fix the problem, we’ll get you what you need another way: we can read it to you over the phone, send it in a message, or help you at the counter.

Then we’ll fix the barrier, or tell you plainly why we can’t yet and what we’re doing about it.

About this statement

We last reviewed this statement and tested the website on October 1, 2026. We check again whenever we change the website, and we’ll update this page when we do.