Statement

Accessibility statement

A plain-English account of where we stand on accessibility, what we're actively working on, and the alternative paths available where parts of our product aren't fully accessible yet.

Last reviewed · April 2026

Our commitment

YesPersonalized is committed to making our products usable by as many people as possible, including people with visual, hearing, motor, and cognitive disabilities. We follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our reference standard, and we treat accessibility as an ongoing process — not a one-off sign-off.

This statement was last reviewed on April 2026 and is updated whenever we ship significant changes to in-scope products or learn about new barriers from users.

What this statement covers

This statement applies to:

  • Our marketing website at yespersonalized.com (homepage, documentation, support, privacy, this page).
  • Our Shopify embedded admin — used by Shopify merchants who install our app.
  • The storefront personalisation widget that runs on Shopify storefronts where merchants have installed our app — this is where end consumers (the merchant's customers) interact with us.
  • Our customer-facing support pages.

Compliance status

Partially compliantwith WCAG 2.1 Level AA. The exceptions and non-compliances below are the items we are aware of. Some of these will be remediated in upcoming releases; others reflect technical constraints we're actively working around.

Areas of full or substantial compliance

  • Marketing pages (homepage, documentation, support landing, privacy, this statement) — built with semantic HTML, proper heading order, labelled form fields, keyboard-operable navigation, and visible focus states. Screen reader compatible with NVDA, VoiceOver, and JAWS in current versions.
  • Embedded admin sections (Templates list, Orders, Products, Settings, Billing, Support) — semantic forms, labels, keyboard navigation, status communicated as text rather than colour alone.
  • Reduced-motion preference — we honour the operating-system setting that asks for reduced motion. If your OS or browser is set to reduce motion, our animations, transitions, and pulsing live indicators are disabled.

Known limitations

We are not yet fully accessible in the following areas. We list them here so you know what to expect, and we'll work with you to find an alternative if any block you.

1. Visual template editor (admin only)

The drag-and-drop template editor uses an HTML canvas for direct manipulation. Canvas elements are inherently difficult to make screen-reader accessible. Today, a screen reader user cannot directly position layers visually. The form-based properties panel for each layer (font, colour, size, conditional rules, position) remains keyboard-operable and screen-reader accessible — it's the canvas-level preview that is not.

Workaround: every visual change you make in the editor is also reflected in the properties panel and the layer list, both of which are accessible. For complex visual layouts, we recommend pairing with a sighted colleague or contacting our support team — we're happy to set up templates on your behalf.

2. Storefront personalisation widget — live preview canvas

The storefront widget shows a live preview of each customer's personalisation on a canvas-rendered product mock-up. As the customer types, the canvas updates. Screen readers cannot read the rendered preview content directly.

Mitigation in place: the widget is form-based — all customer input happens in standard HTML <input> and <textarea> fields with proper labels. The customer can complete their personalisation and add it to cart entirely without seeing the canvas. Validation messages, character limits, and conditional layer hints are announced via accessible status text.

Active improvement: we're prioritising live announcement of preview updates via aria-live regions in the next widget release, so assistive technology users get audible confirmation when their input changes the visual output.

3. Free Roam Zone editor

The Free Roam Zone (a sandbox letting customers add their own text, photos, stickers, and shapes anywhere within a defined region) is currently mouse / touch driven. Direct keyboard manipulation of placed elements isn't supported.

Workaround: merchants who set up Free Roam Zones on their products can offer an alternative configurator (a custom-design service or email-based briefing) for customers who can't use the visual interface. If your store sells personalised goods that rely on Free Roam Zones, please contact our support team — we can advise on alternative flows.

4. Image-upload zones

Some image-upload regions in the storefront widget are styled as click areas rather than native <input type="file"> labels. These are triggered on click but may not be reachable via keyboard or announced consistently by screen readers.

Active remediation: this is on our backlog and will be fixed by wrapping each upload zone in a proper <label> linked to a visually hidden file input.

5. Colour contrast in some marketing surfaces

Some accent text (our brand coral on cream backgrounds) has not been independently audited against the WCAG 4.5:1 contrast threshold. Where we've identified possible contrast issues, we'll adjust in upcoming releases.

How we test

We use a combination of:

  • Automated checks (Lighthouse, axe-core) on every meaningful UI change
  • Manual keyboard navigation testing
  • Screen reader spot-checks with NVDA on Windows and VoiceOver on macOS / iOS
  • Reduced-motion preference testing
  • Real user feedback via the channels below

We have not yet commissioned a third-party VPAT (Voluntary Product Accessibility Template). When we do, the result will be linked here.

Compatibility

We test against the most recent versions of the following browser and assistive tech combinations:

  • Chrome (Windows, macOS) with NVDA
  • Safari (macOS, iOS) with VoiceOver
  • Firefox (Windows, macOS) with NVDA
  • Edge (Windows) with Narrator

Older browser versions, or browsers that don't support modern web platform features (CSS Grid, Custom Properties, ES2020), may render the site less accessibly. We don't actively block them — they will likely degrade rather than break.

Reporting an accessibility barrier

If you encounter a part of YesPersonalized that you can't use because of an accessibility issue, please tell us. We will:

  • Acknowledge your message within one working day.
  • Where possible, provide a workaround (manual support, email-based assistance, or a sighted-helper walkthrough) so you can complete what you came to do.
  • Add the issue to our remediation backlog with an estimated timeline.

Contact us at yp-accessibility@allthe.com or open a support ticket via our support page.

Enforcement

If you're a UK customer and you're unhappy with how we respond to an accessibility complaint, you can contact the Equality Advisory and Support Service (EASS).

EU customers are covered by the European Accessibility Act(in force from 28 June 2025). Each member state has a designated enforcement body — we'll cooperate fully with any legitimate enquiry from those bodies.

Standards we measure ourselves against

  • WCAG 2.1 Level AA (target standard)
  • EN 301 549 (the European harmonised accessibility standard, which references WCAG 2.1)
  • UK Equality Act 2010 reasonable-adjustment guidance

Document control

This statement was prepared in accordance with the model statement format set out by the European Commission for in-scope services under the European Accessibility Act. It will be reviewed on a rolling six-month schedule, and immediately if material changes are made to the product.

Statement last reviewed: April 2026.