Boba.guide accessibility statement.
Boba.guide is committed to making its content easier to access, understand and navigate for people with different abilities, devices, assistive technologies and browsing preferences.
What is Boba.guide doing to support accessibility?
Boba.guide aims to provide a clear, readable and navigable experience across desktop, tablet and mobile devices. Accessibility is considered in page structure, writing, visual design, links, images, forms and ongoing site maintenance.
We recognize that accessibility is an ongoing process rather than a one-time task. As the site grows, new pages, tools, advertising and third-party features may require additional testing and improvement.
Accessibility features we aim to maintain
Clear heading structure
Pages use descriptive headings intended to help readers and assistive technologies understand the hierarchy and move between sections.
Readable content
We aim to use plain language, short paragraphs, sufficient spacing and layouts that remain usable at different screen sizes.
Meaningful links
Link text should describe the destination or purpose rather than relying only on vague phrases such as “click here.”
Image descriptions
Informative images should include appropriate alternative text when a visual contributes meaning that is not already available in nearby text.
Responsive layout
Pages are designed to adapt to mobile, tablet and desktop screens without requiring a single fixed display size.
Keyboard usability
Navigation, links and interactive controls should be operable without relying exclusively on a mouse or touch input.
Color, contrast and text presentation
We aim to maintain sufficient contrast between text and backgrounds, avoid using color as the only way to communicate meaning and preserve readable text sizes across common devices.
Readers may use browser zoom, operating-system display settings or reader tools to enlarge text. The site should remain usable at reasonable zoom levels, although some third-party content may behave differently.
Design should support the content
Decorative styling should not make important information difficult to read. When visual appearance and usability conflict, the clearer and more accessible presentation should take priority.
How editorial content is made easier to understand
Direct explanations
Important answers are placed near the beginning where practical and explained without unnecessary jargon.
Descriptive sections
Long pages are divided into focused sections so readers can scan and locate relevant information.
Tables and lists
Structured elements are used when they make comparisons, steps or options easier to understand.
Definitions in context
Specialized boba, tea, ingredient and preparation terms should be explained where readers need them.
Accessible link purpose
Internal links should make sense in context and help readers predict what they will find next.
Nonvisual meaning
Critical instructions or conclusions should not depend only on an image, color, icon or visual position.
How are visuals handled?
Informative photographs, diagrams and illustrations should include useful alternative descriptions. Decorative visuals may use empty alternative text so assistive technology can skip them.
Captions may be used when they add context, attribution or information that should be visible to all readers. Text should not be placed only inside an image when it can reasonably be presented as regular page content.
What about multimedia?
When Boba.guide publishes meaningful video or audio, we aim to provide captions, transcripts or an equivalent text explanation where reasonably possible.
Embedded third-party media may not always meet the same accessibility standards and may depend on the controls provided by the external platform.
How should interactive controls work?
Forms and controls should use understandable labels, visible instructions, clear error messages and predictable behavior. Required information should not be indicated only by color.
We aim to preserve visible keyboard focus and logical navigation order for links, buttons and form fields.
Can external services create barriers?
Maps, videos, advertisements, analytics interfaces, consent platforms and other third-party tools may be controlled by external providers. Their accessibility may vary.
When a third-party feature creates a barrier, we will consider available alternatives, configuration changes or additional text-based information.
Where might accessibility problems still occur?
Older content
Pages created before current standards may contain inconsistent headings, image descriptions or formatting.
Third-party embeds
External media, maps, advertising and widgets may not provide complete keyboard or screen-reader support.
Documents and downloads
Some downloadable files may require further remediation to work well with assistive technologies.
Dynamic updates
New features or design changes may introduce issues that are not immediately identified.
Browser differences
Accessibility can vary among browsers, devices, operating systems and assistive-technology combinations.
Complex visual content
Some charts, comparisons or detailed images may require additional text explanation to be fully accessible.
How can an accessibility problem be reported?
Send a message to info@boba.guide with the page URL, a description of the problem and the device, browser or assistive technology involved when known.
Screenshots or a short explanation of what you expected to happen can help us identify the issue. Please do not send unnecessary sensitive personal information.
We welcome specific feedback
Helpful reports identify the exact page, feature or control involved. We review credible accessibility concerns and prioritize issues that block access to important content or essential site functions.
What happens after a report is received?
We may reproduce the issue, review the relevant code or content, test an alternative presentation and determine whether the problem can be fixed directly or requires support from a third-party provider.
Resolution time depends on severity, complexity, available resources and whether an external service is involved.
Can information be provided another way?
When a barrier cannot be resolved immediately, we may provide the requested information in an alternative accessible format when reasonably possible.
The available alternative depends on the content, rights, technical limitations and nature of the request.
How is accessibility maintained over time?
Accessibility may be considered during design changes, content reviews, template updates, image preparation, navigation planning and quality-control checks. We may also revise older pages when barriers are identified.
Template review
Shared page layouts and navigation components may be checked when significant design changes are made.
Content review
Headings, links, image descriptions and structured information may be corrected during editorial updates.
User feedback
Reader reports help identify practical barriers that automated checks may not detect.
Policies connected to accessibility and site use
Each destination below appears once and addresses a separate part of our responsibilities.