Accessibility Statement

Our commitment

Accessibility is part of how we think about a clean, orderly serving system — the same care we put into a tool that sits within reach, we try to put into a store that everyone can use. We are committed to making the Bakxyshake website usable by as many people as possible, regardless of ability, device, or the assistive technology they rely on.

We treat accessibility as an ongoing responsibility rather than a one-time task. As we add products, update policies, and refine the store, we aim to design and build in a way that keeps content perceivable, operable, understandable, and robust. Where we discover a barrier, our goal is to understand it, prioritize it, and fix it within a reasonable time.

This is a working document. It reflects the current state of our efforts and will change as we make improvements and as standards evolve. We welcome the input of people who use our site with assistive technology, because real experience tells us more than testing alone.

Conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG is an internationally recognized standard, published by the World Wide Web Consortium, that describes how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive differences. Level AA is the level commonly adopted as a practical target for public websites.

The four principles behind WCAG guide our work: content should be perceivable (able to be presented in ways people can sense), operable (usable through different inputs), understandable (clear and predictable), and robust (reliable across browsers and assistive tools). Where we reference this target elsewhere, we mean these principles applied at Level AA.

Measures we take

We build accessibility into the way we design and maintain the store rather than treating it as an afterthought. Practical measures we apply across the site include the following.

• Semantic structure. We use headings, landmarks, lists, and meaningful markup so the page has a logical order that assistive technology can follow.
• Text alternatives. We provide descriptive alternative text for meaningful images and mark purely decorative graphics so they can be ignored by screen readers.
• Colour and contrast. Our palette is chosen for a light, legible reading experience, and we aim for sufficient contrast between text and its background across the store.
• Visible focus. Interactive elements are designed to show a clear focus indicator so people navigating by keyboard can see where they are.
• Labelled controls and forms. Inputs, buttons, and form fields are labelled so their purpose is clear, and status messages are announced where appropriate.
• Responsive, resizable layouts. Pages are built to reflow on different screen sizes and to remain usable when text is enlarged.
• Reduced-motion support. We honor the operating-system preference for reduced motion and disable non-essential animation for visitors who request it.

These measures are applied as consistently as we can across templates and content, and they inform how we review new pages before they go live.

Ongoing efforts

Accessibility work is continuous. As the store grows and content changes, we keep reviewing and improving rather than assuming a page stays accessible forever. Our ongoing efforts include regular self-assessment of key pages and flows, checking new content against our accessibility measures before and after it is published, and correcting issues as we find them or as they are reported to us.

We use a combination of manual review and automated checks, and we test with keyboard-only navigation and with assistive technology where we can. Automated tools catch some issues, but many accessibility questions require human judgement, so we treat tooling as a support to review rather than a replacement for it. We also factor accessibility into decisions about design changes and new features.

Because parts of the store rely on platform and third-party components we do not fully control, some improvements depend on updates from those providers. Where that is the case, we monitor for fixes and apply them, and in the meantime we look for ways to reduce the impact on visitors.

Supported assistive technology

We aim for the store to work with current versions of widely used browsers and assistive technologies. In practice this means we design and test toward combinations such as the following, used on recent operating systems.

• Recent versions of mainstream browsers, including Chrome, Firefox, Safari, and Edge, on desktop and mobile.
• Common screen readers, including those built into operating systems and popular standalone readers on desktop and mobile.
• Screen magnification and browser zoom, along with operating-system text-size and display settings.
• Keyboard-only navigation and alternative input methods that emulate a keyboard.
• Operating-system preferences such as reduced motion and increased contrast, where the browser exposes them to the page.

We focus our testing on current and recent versions, because older or unusual combinations may not fully support the modern techniques the site relies on. If you use a specific assistive technology and encounter difficulty, telling us which browser and tool you use helps us reproduce and address the problem.

Keyboard navigation

The store is designed to be operated with a keyboard alone, without requiring a mouse or touch. Interactive elements — links, buttons, form fields, and menus — are reachable in a logical order using the Tab key to move forward and Shift plus Tab to move back, and are activated with the Enter or Space keys as appropriate to the control.

• A visible focus indicator shows which element currently has focus as you move through the page.
• The reading and focus order is intended to follow the visual and logical order of the content.
• Controls that open menus or reveal content are built to be operable from the keyboard, and confirmation messages are placed so they can be found after an action.

If you find a control that cannot be reached or operated with the keyboard, or a point where focus becomes trapped or lost, please tell us using the feedback details below and describe the step where it happened. Keyboard issues are a priority for us because they affect many assistive-technology users.

Known limitations and remediation

Despite our efforts, some parts of the store may not yet fully meet our WCAG 2.1 AA target. We would rather be transparent about this than imply the site is flawless. Areas where limitations can arise include the following.

• Third-party and platform components. Some interactive elements provided by our platform or by external services may not fully match our accessibility standards until those providers update them.
• Rich or dynamic content. Newly added pages, promotions, or interactive features may occasionally ship with issues that we correct once identified.
• Legacy content. Older images or documents may lack complete text alternatives, which we improve as we revisit them.
• Embedded media. Media supplied by third parties may not always carry captions or descriptions that we can control directly.

How we remediate. When we find or are told about a barrier, we assess its impact, prioritize it — giving weight to issues that block core tasks such as browsing the catalog, reading policies, or contacting us — and work to resolve it within a reasonable time. Where a fix will take longer, we look for an interim way to provide the same information or function, and we are glad to help directly in the meantime through the contact details below.

Third-party content

Some content and functionality on the store is provided by third parties, including our e-commerce platform, fonts and other embedded resources, and any external services we use to run the site. We do not always have full control over the accessibility of third-party components, and their conformance can change when those providers update them.

Where third-party content falls short of our standards, we look for accessible alternatives, raise the issue with the provider where we can, and try to reduce the impact on visitors in the meantime. If a barrier you encounter comes from a third-party element, telling us where it appears still helps, because we can often find another route to the same information or press for a fix.

Information in other formats on request

If you need information from this site — such as a policy, product detail, or ordering instruction — in a format that works better for you, we are happy to help. Depending on the request, we can provide the content in an alternative way, read information to you, or talk you through a task directly.

To ask for information in another format, contact us using the details below and tell us which content you need and the format that would help. We will do our best to respond promptly and to find a workable way to give you the same information other visitors receive.

Feedback process

Your feedback helps us find and fix barriers we may have missed. If you run into difficulty using any part of the Bakxyshake store, or you have a suggestion for making it more accessible, please tell us. To help us understand and reproduce the issue, it is useful to include:

• The page or task where the problem happened, and what you were trying to do.
• The browser, operating system, and any assistive technology you were using, including versions if you know them.
• A short description of what went wrong and what you expected instead.

You can send feedback using the details in the contact section, or by completing the short form below. We aim to acknowledge accessibility feedback promptly and to follow up within two business days. Where a reported issue needs more work, we will let you know that we are addressing it and, where we can, offer a way to get the information or complete the task in the meantime.