Accessibility Statement

Rex Commerce® (rex.aeo-rex.com), operated by AEO-Rex Ltd, is committed to making this website accessible to as many people as possible, regardless of disability, assistive technology, or device. This statement explains our conformance target, what we have done, what we know is imperfect, and how to give us feedback.

Conformance status

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Most of the site meets that standard. Where it does not, the gaps are listed below in the "Known issues" section, with timelines for remediation.

This is a self-assessment. We have not yet commissioned an external audit, but plan to before the Q3 2026 cohort launch.

What we have done

• Semantic HTML. The site uses native HTML elements (<header>, <nav>, <main>, <article>, <section>, <footer>) and a single H1 per page, so screen readers can navigate by landmark and heading.
• Keyboard navigation. Every interactive element (links, form fields, FAQ toggles) is reachable and operable using Tab, Shift+Tab, Enter, and Space.
• Visible focus. Browser-default focus rings are not suppressed.
• ARIA labelling. Form fields have associated aria-label values where labels are not visible. FAQ toggles use aria-expanded. Decorative icons are marked aria-hidden="true".
• Colour contrast. Body text on the navy background meets WCAG AA contrast ratios (approximately 11:1). Cyan accent text on navy meets AA-large but is reserved for headings, large eyebrows, and links — not body copy.
• Responsive layout. The site reflows at 320px viewport width without horizontal scrolling, supports browser zoom up to 400%, and respects prefers-reduced-motion via the system default (no auto-playing animations beyond a slow pulse on a single status dot).
• Alt text. All informational images have alt attributes. Decorative images use alt="".
• Form errors. The waitlist form uses native HTML5 validation with required and type="email", which produces accessible browser-level error messages.
• Link clarity. External links open with rel="noopener" and are visually distinguished by an arrow (↗) so screen-reader users and sighted users alike know they are leaving the site.

Known issues

• Hero counter animation. The "50M" counter on the homepage animates from 0 on first view. Users with prefers-reduced-motion set will see it animate. We will add a reduced-motion fallback by July 2026.
• FAQ accordion. The accordion uses height transitions, which can be slow on older devices. The transition is short enough not to be a barrier, but we are evaluating <details>/<summary> as an alternative.
• Cookie/transparency notice. The dismiss button is keyboard-reachable, but the notice does not trap focus while open. This is intentional (the notice is not modal) but we are aware some users may prefer focus-trap behaviour.

If you encounter an accessibility barrier not listed here, please tell us — see the next section.

Feedback and contact

If you have an accessibility issue with any page on rex.aeo-rex.com, or you need information from the site in a different format (large print, audio, plain text), please email:

shanazbegum@aeo-rex.com

Subject line: Accessibility feedback. We aim to respond within 5 working days. Where the issue is critical, we will respond within 48 hours.

Enforcement

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations that apply to public sector websites in the UK. Rex Commerce® is a private-sector commercial site, so the public-sector regulations do not directly apply, but we voluntarily aim to meet the same WCAG 2.2 AA standard. If you have an accessibility complaint about this site, contact us first using the email above. If you remain dissatisfied, you may seek further advice from the Equality Advisory and Support Service.

Technical specifications

The accessibility of rex.aeo-rex.com relies on the following technologies to work with the particular combination of web browser and any assistive technologies installed on your computer:

• HTML5
• WAI-ARIA
• CSS3
• JavaScript (used progressively — the site's core content is fully usable without JavaScript enabled)

Preparation of this statement

This statement was prepared on 9 May 2026 using a self-evaluation against WCAG 2.2 Level AA success criteria. It was last reviewed on 9 May 2026.