Accessibility Statement

1. Scope

This Statement covers the Orbit Commerce marketing website at orbitcommerce.net, the vendor dashboard, and other Orbit Commerce-operated web properties. It does not cover the content, custom code, or third-party apps that a Vendor adds to an individual Storefront, which are configured and operated by the Vendor or a third party.

The storefront technology we provide — including our themes, checkout, and the pages our page builder generates — is within the scope of our accessibility commitment in section 2, because Vendors can only make their Storefronts accessible if the platform underneath them is. Section 5 explains how responsibility is shared.

2. Our Commitment

We want the Orbit Commerce platform to be usable by as many people as possible, including people who use assistive technology. We treat accessibility as part of our design and engineering practice and we aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at conformance level AA for the public-facing parts of our platform.

We also comply with our duty to make reasonable adjustments under sections 20 and 21 of the Equality Act 2010 where they apply.

For e-commerce services provided to consumers in the European Union, the European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025. Where the Service is used to sell to EU consumers, we work towards the requirements of the European harmonised standard EN 301 549 (which incorporates WCAG at level AA) for the storefront technology we provide, and we support Vendors in meeting their own obligations under the European Accessibility Act as implemented in the member states where they sell.

3. What We Do

• we design with sufficient colour contrast, scalable text, and visible focus indicators;
• we support keyboard-only navigation on the most-used flows;
• we use semantic HTML and ARIA where appropriate so screen readers can navigate the site;
• we provide alternative text on meaningful images;
• we use captions or transcripts for video content we publish, where reasonably practicable;
• we run automated accessibility checks as part of our development workflow and manual reviews on significant releases.

4. Known Limitations

We are honest that not every page or feature currently meets WCAG 2.2 AA. Known areas where we are still working towards full conformance include:

• some complex interactive components in the page builder and admin tooling may have incomplete keyboard or screen-reader support;
• some third-party content embedded on our pages (for example, video, embedded widgets, or live chat) may not match the level of accessibility we aim for in our own code;
• some images may lack alternative text, particularly in older blog posts or user-generated content.

We track these issues and address them as part of our ongoing development. We do not commit to a specific fix date for any individual issue.

5. Storefronts

Accessibility of a live Storefront is shared between us and the Vendor. We are responsible for the accessibility of the storefront technology we supply: our themes as shipped, the checkout flow, and the markup our page builder generates. The Vendor is responsible for what they add: the content they publish (including image alt text and document uploads), the apps they install, theme customisations, and any custom code.

Vendors that sell to consumers in the UK should consider their own obligations under the Equality Act 2010, and Vendors that sell to consumers in the European Union should consider their obligations under the European Accessibility Act, which has applied since 28 June 2025. We make accessibility-aware themes and guidance available, but we cannot guarantee the accessibility of any individual Storefront as configured by its Vendor.

6. Reporting an Accessibility Issue

We welcome feedback. If you find an accessibility issue, or if you need information in an alternative format (for example, large print, plain text, easy read, audio recording, or braille), please contact us:

We aim to acknowledge accessibility reports within five (5) business days. We will consider any reasonable adjustment we can make. Whether we can implement a specific change will depend on its proportionality, cost, and the impact on the wider service.

7. Enforcement

If you are not satisfied with our response to an accessibility complaint, you may contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com or take advice from the Equality and Human Rights Commission. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to us as we are a private-sector business.

8. Preparation of this Statement

This Statement was prepared on the date shown above based on a self-assessment against WCAG 2.2 AA, internal manual reviews, and automated tooling. We review and update this Statement at least annually.