Accessibility Statement

A website is only useful if everyone can use it. Here’s where we stand, and how to tell us when we get it wrong.

Last updated: [EDITABLE — effective date]

Our Commitment

Block Stream Entertainment wants everyone to be able to browse our products, place an order and get support — regardless of disability, assistive technology or device. We treat accessibility as an ongoing part of building the site rather than a one-off project, and we fix barriers when they’re reported to us.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. That is the standard we design and build against, and the benchmark we use when reviewing the site.

What We’ve Done.

Semantic HTML structure with a logical heading order on every page
Text alternatives on meaningful images and icons
Colour contrast checked against WCAG AA for body text and key controls
Form fields paired with visible, persistent labels rather than placeholder-only text
Keyboard-operable navigation, buttons, accordions and form controls
A visible focus indicator on interactive elements
Layout that reflows to a single column and remains usable when zoomed
Touch targets sized for comfortable use on phones and tablets
Motion kept subtle, with reduced-motion preferences respected
Status messages announced in text rather than communicated by colour alone

What We’re Still Working On.

We’d rather tell you where the gaps are than claim there aren’t any.

Auditing every page against WCAG 2.1 Level AA and logging what we find

Improving the reading order of complex, image-heavy product sections

Adding more descriptive alternative text to product photography

Reviewing the checkout and Stripe-hosted payment flow, which sits partly on a third party's platform

Payment is handled on Stripe’s hosted checkout, which sits outside our website and is governed by their own accessibility work. If you hit a barrier there, tell us and we’ll take the order another way.

Tell Us About a Barrier.

If any part of this site is difficult or impossible to use, please say so. Describe what you were trying to do and what happened — we treat accessibility reports as bugs, not feedback, and we aim to respond within five business days.