Last updated: April 19, 2026
We want Bark & Bottle to be easy to use for everyone, including people who rely on assistive technology. This page describes our commitment to accessibility, where we are today, and how to let us know when something isn’t working.
Our commitment
We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the current version of the international accessibility standard as of 2026. We treat accessibility as a steady practice rather than a one-time audit — every design and development change gets a basic check for color contrast, keyboard navigation, semantic markup, and screen-reader compatibility.
We also recognize our obligations to users in California under the Unruh Civil Rights Act (Cal. Civ. Code § 51) and to users nationwide under the Americans with Disabilities Act. The commitments and practices described on this page apply to all visitors.
What we’ve done
- Semantic HTML throughout (headings in order, landmarks, lists where appropriate)
- Keyboard-accessible navigation, search, and forms
- Visible focus states that meet contrast requirements
- Alternative text on informative images
- A “skip to content” link for keyboard users
- Color contrast that meets AA for body text and interactive elements
- Target sizes and consistent help mechanisms reviewed against WCAG 2.2 additions
Known limitations
Bark & Bottle is a work in progress. We know that:
- Some older user-submitted winery descriptions may not have complete alternative text on every image.
- A few embedded third-party tools (maps, forms) may not meet the same standards we hold our own pages to, and we’re working with vendors to improve them.
If you run into a specific barrier, we’d like to hear about it so we can fix it.
Report a problem
Email roger@northandvine.net with a short description of the page and what went wrong (a URL and screenshot help). If email isn’t accessible for you, please use any of the contact forms on the site and we’ll follow up in whatever format works best for you. We aim to respond within five business days.
Ongoing work
We run periodic automated accessibility checks and manual keyboard / screen-reader tests on key pages. When we find issues, we fix them and update our checklist so the same kind of issue doesn’t ship again. As standards evolve — for example, when WCAG is updated — we review our practices against the new guidance.