Accessibility Statement
Effective September 22, 2026 · Last updated September 22, 2026
BudFinderKC should work for everyone, including people who use a screen reader, navigate by keyboard, or rely on other assistive technology. This statement describes what we've built toward that, and where we know we still fall short.
Our commitment
We build BudFinderKC to meet WCAG 2.2 Level AA, which incorporates and exceeds WCAG 2.1 AA. That's our target for every page we build, not just the ones most likely to get noticed.
What we've done
Accessibility is built into the site's foundation, not bolted on after the fact.
- Semantic HTML structure — real headings, landmarks, and lists, so assistive technology can navigate the page the way it navigates any well-built site.
- A "Skip to main content" link for keyboard users, so you can jump straight past the navigation on every page.
- Full keyboard operability on filters, forms, and navigation, with visible focus indicators.
- A contrast pass on our color palette, including the green tones that are a chronic weak spot on cannabis sites.
- Respect for reduced-motion preferences — if your system asks for less motion, we give you less motion.
- Alt text on listing photos and logos: businesses are asked to describe their own images when they upload them, and we review submissions that arrive without one.
What we haven't fully solved
One thing, honestly, isn't there yet.
- Ordering and detailed menus happen on each dispensary's own website, which we link out to — we don't control, and can't fully vouch for, the accessibility of a third-party site once you leave ours.
The map
Our interactive map is still the hardest part of the site to use well by keyboard or screen reader — panning, zooming, and reading a pin's details are all easier with a mouse. So every page that shows the map also shows the same listings as a plain, fully accessible list: on /dispensaries a button switches between the two views, and elsewhere the list sits right alongside the map. If you never touch the map, you're not missing anything it knows.
No overlay widget
We don't use an accessibility overlay or widget. Widgets like that paper over problems in the underlying code rather than fixing them, and they hold up poorly under real assistive-technology use — we'd rather fix the page than dress it up.
Ongoing checks
We run automated checks and manual passes with a screen reader and a keyboard alone as we build, and we track any barrier we find through to resolution.
Reporting a barrier
If something on BudFinderKC doesn’t work for you, tell us: accessibility@budfinderkc.com, with the page URL and a description of what happened, and what assistive technology or browser you were using if you know it. We aim to respond within 5 business days and to fix confirmed barriers on a timeline that matches their severity — a broken form gets fixed faster than a cosmetic contrast issue.
This statement
This statement was last reviewed September 22, 2026, alongside a full audit against WCAG 2.2 AA (automated checks plus a manual keyboard/screen-reader pass across every route). As the site changes, we’ll keep it current.
Questions about this page? Write to hello@wabbit.com or use the contact page.