Making Boba.guide easier to use
Accessibility Statement
Boba.guide is intended to be useful to as many people as reasonably possible, including readers who navigate differently, enlarge text, use keyboards or assistive technologies, need stronger visual contrast, or access the site from smaller screens.
Accessibility is not a one-time badge we can add to a website and forget. Content changes, layouts evolve, plugins are updated, new pages are published and real users encounter combinations of devices and assistive technologies that cannot all be predicted from an editor screen.
For that reason, this statement explains both the accessibility practices we build into Boba.guide and how to tell us when something is not working for you.
Our approach
Accessibility Is Part of How We Build the Site
We aim to make accessibility a practical part of page structure, typography, links, navigation, imagery and responsive design rather than treating it as a separate decorative feature.
Web Content Accessibility Guidelines (WCAG) are an important reference for this work. They provide a structured framework for thinking about perceivable content, operable controls, understandable interfaces and robust web markup.
We do not use that reference to make an unsupported claim that every Boba.guide page has been independently audited or formally certified against a particular conformance level.
What we design for
The Accessibility Practices We Try to Apply Across Boba.guide
Different accessibility needs interact with different parts of a page, so there is no single switch that makes everything accessible. These are some of the areas we pay attention to as the site is built and updated.
Links and interactive controls should not depend only on a mouse
Interactive elements should be reachable and usable through normal keyboard navigation where the underlying feature supports it. Keyboard focus should remain visible so a user can tell which element is currently active.
We avoid intentionally suppressing focus indicators for cosmetic reasons.
A link should look like a link
Inline links should remain distinguishable from surrounding body text. We use visible link color, underlining and separate states for normal, visited, hover and keyboard focus rather than deliberately hiding navigation inside the typography.
This applies on light, tinted and dark backgrounds.
Content should remain readable without being squeezed into tiny columns
Boba.guide pages are designed to simplify as screens become narrower. Multi-column editorial layouts should stack logically rather than forcing text into narrow strips or requiring whole-page horizontal scrolling.
Tables and comparison structures may need a different presentation on small screens rather than simply shrinking the desktop version.
Visual hierarchy should also make structural sense
Pages should use descriptive headings and a logical reading order. A heading is not just a larger font: it should describe the section that follows and help readers navigate longer material.
Where jump navigation is used, its links should point to real sections rather than decorative placeholders.
Informative images should have meaningful text alternatives
Images that contribute information should receive alt text appropriate to what the image adds to the page. Decorative wording, production instructions and keyword stuffing do not belong in alternative text.
The usefulness of the text alternative matters more than mechanically describing every visible object in a photograph.
Typography should support reading rather than fight it
We aim for readable text sizes, practical line lengths, sufficient spacing and layouts that can adapt when content wraps. We do not intentionally force ordinary article text into extremely narrow tracks or fixed-height boxes.
Important information should not disappear into the design
Text and interactive elements should remain visually distinguishable from their backgrounds. Dark sections require their own readable link and text states instead of inheriting colors designed for a white page.
We also avoid relying on a very subtle color difference as the only signal that body text is clickable.
Information should not require decorative motion to make sense
Boba.guide’s editorial pages are designed primarily around text, images and static information structures. We avoid making essential content dependent on unnecessary animation, sliders or visual effects.
Accessibility also applies to information
Clear Content Is Part of an Accessible Experience
Technical accessibility matters, but a perfectly focusable interface can still be difficult to use if the information itself is confusing.
Headings should tell readers what a section actually explains rather than relying on vague labels that only make sense after the section has been read.
Specialist terminology can be useful, especially when explaining tea, ingredients or regional boba vocabulary, but unfamiliar terms should be explained rather than used as a barrier to understanding.
Where practical, links should tell the reader what they will find after following them rather than relying on repeated vague labels such as “click here.”
When readers need to compare drinks, toppings, ingredients, prices or other information, the format should make the comparison clearer rather than placing decorative styling ahead of comprehension.
A careful claim, not a certification badge
About WCAG and Conformance
Boba.guide uses accessibility principles reflected in the Web Content Accessibility Guidelines as an important reference when building and reviewing the site.
However, unless and until a specific version of the site has completed the testing necessary to substantiate a formal conformance statement, we do not claim that every page or third-party component has been independently certified as fully conforming to WCAG 2.2 AA or another conformance level.
That distinction is intentional. Accessibility is more useful when it is treated as an ongoing responsibility than when a site makes a broader claim than its testing can support.
If formal testing or the site’s technical status changes, this statement can be updated to describe that accurately.
Help us reproduce the barrier
If Something Is Difficult or Impossible to Use, Tell Us What Happened
A short, specific accessibility report can be much more useful than a general message saying that a page is broken.
Tell us which Boba.guide page or feature caused the problem.
For example: opening a navigation link, reading a table, using a menu, activating a button, increasing text size or moving through the page with a keyboard.
Describe the barrier itself: focus disappeared, text overlapped, a control could not be reached, content was cut off, contrast was insufficient, an image lacked a useful text alternative, or another issue prevented access.
If you know them, tell us the device, operating system and browser you were using. This can help reproduce layout or interaction problems.
If relevant and you are comfortable sharing it, tell us the screen reader, magnification software, voice-control tool, keyboard setup or other assistive technology involved. You do not need to disclose a disability or medical condition.
If there is an alternative format or specific change that would allow you to use the content, tell us. That information can make the report much easier to act on.
Report an accessibility problem
Contact Boba.guide About an Access Barrier
Send accessibility feedback to:
info@boba.guideYou can include as much or as little technical detail as you have. The most important information is what you were trying to access and what stopped you.
For a general editorial question, copyright matter, privacy request or another type of enquiry, use our Contact Boba.guide page instead.
Where accessibility can become more complicated
Third-Party Features and External Content
Some parts of a website may depend on software, embeds, advertising systems, consent tools, external services or other components that are not developed entirely by Boba.guide.
Third-party interfaces can behave differently
A control supplied by a plugin or external service may not respond exactly like Boba.guide’s own editorial markup. If a third-party component creates a barrier on our site, we still want to know where it occurs.
External websites have their own accessibility practices
When Boba.guide links to an official menu, regulator, source or another outside website, we cannot control that external site’s design or accessibility. The presence of an external link should not be interpreted as a claim about the accessibility of the destination.
Older content may not always match newer page standards
As Boba.guide evolves, older pages or legacy components may need additional review. Reports about older material are useful because they can identify areas that should be prioritized.
Accessibility is maintenance
How Accessibility Fits Into Ongoing Site Work
We treat accessibility as something that can improve as pages are created, rebuilt and corrected rather than as a claim that can never change.
Use accessible patterns when creating pages
That includes semantic structure, readable typography, visible links and focus, responsive layouts and useful text alternatives where images carry information.
Look for layout and interaction problems during page QA
Desktop appearance alone is not enough. Narrow screens, keyboard states, contrast and content wrapping can expose problems that are not obvious in a large editor preview.
Use reader feedback to find barriers our own checks missed
Automated checks and editorial review cannot reproduce every real user’s setup. Accessibility feedback adds information that a development checklist may not reveal.
Correct the underlying pattern where possible
If the same accessibility problem can affect many pages, the more useful fix is the shared design or component rather than a cosmetic patch on one paragraph.
A practical standard
Accessibility Means Being Able to Use the Information
The purpose of Boba.guide is to make a complicated food and drink world easier to understand. That goal is undermined if the page itself creates an unnecessary barrier between a reader and the information.
We will not claim that a written accessibility statement makes every page perfect. We will continue to use accessible design principles, improve the site’s patterns as they evolve and take specific barrier reports seriously.
If Boba.guide is preventing you from accessing something you need, email info@boba.guide.