Accessibility Statement

Conformance target

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2, Level AA (opens in a new tab). WCAG provides the core web criteria used by EN 301 549, but this target does not by itself establish legal conformity. Our internal design system records the concrete rules we apply: a measured colour-contrast matrix, visible focus indicators, minimum target sizes, reduced-motion support, and correct semantic structure.

What we do to support access

• Text and interface colours are checked against WCAG contrast ratios on every surface.
• Interactive controls are designed to show a visible keyboard focus indicator.
• Core menus, filters, and dialogs are designed for keyboard-only operation.
• A "Skip to main content" link is the first focusable element on every page.
• Pages use landmark regions, a single main heading, and a logical heading order.
• Images that convey meaning have text alternatives; decorative images are hidden from assistive technology.
• Content reflows without horizontal scrolling down to 320 px wide and remains usable at 200% text zoom.
• Animation and motion are reduced or removed when your system requests reduced motion.
• The interface is available in multiple languages, with the page language exposed to assistive technology.

Known limitations

We are aware of the following gaps and are working to close them:

• Some secondary Market Finder controls still use the older visual system. Their trigger state, accessible names, selected state, Escape behavior, focus return, and keyboard option navigation have been upgraded, but formal assistive-technology validation is still pending.
• A dated public browser and assistive-technology test matrix is not yet available. Manual verification remains part of the release checklist while independent testing is planned.
• Some complex catalogue relationships are rendered as dense lists and tables. They remain keyboard-scrollable but may require additional navigation when zoomed on a narrow screen.
• Item artwork is served from third-party content delivery networks. When an image fails to load, a labelled placeholder is shown in its place.

Compatibility

The site is designed to work with current versions of major browsers (Chrome, Firefox, Safari, Edge) and screen readers (NVDA, JAWS, VoiceOver), with keyboard-only navigation, browser zoom, and operating-system reduced-motion settings.

Assessment method

This statement is based on a repository-level self-evaluation against our WCAG 2.2 AA target. Static accessibility regression checks run in the build pipeline. The release process also requires keyboard, screen-reader, zoom, motion, and contrast checks, but the results are not yet published as a dated matrix. A third-party audit and testing sessions with disabled users are planned and will be reflected here.

Give feedback or report a barrier

If you find something on this site that is hard to use, blocks you, or does not work with your assistive technology, please tell us. Include the page address, what you were trying to do, the browser and assistive technology you were using, and the problem you hit.

Email albertopeisan+cs2sticker@gmail.com. We aim to acknowledge accessibility reports within five working days and to agree a fix or a workaround with you.

Escalation

If you contact us about an accessibility problem and are not satisfied with our response, you may be able to raise the matter with the accessibility enforcement body in your country. Within the European Union, national enforcement bodies handle complaints under the Web Accessibility Directive and the European Accessibility Act.