Accessibility statement

Target: WCAG 2.2 Level AALast audited 28 August 2026 Next audit February 2027Auditor: external, plus in-house per release

1. Our commitment

Shopping here should work with a screen reader, a keyboard, one hand, low bandwidth, or all of the above at once. We treat accessibility as a release blocker, not a nice-to-have: every page ships through contrast, focus-order and landmark checks, and this statement lists our failures as openly as our successes — with dates attached.

2. What's working

Keyboard everything. Full purchase flow — browse to pay — with a visible focus ring on every interactive element and a skip-to-content link on every page.
Screen-reader structure. One h1 per page, ordered headings, labelled landmarks, and live-region announcements for cart adds and form errors.
Product images. Alt text written by the photography team describes the product, not the vibe — "olive-green quilted parka, knee length, toggle hood".
Forms. Every field has a persistent label, errors are announced in text (never colour alone), and validation waits for you to leave the field — no yelling mid-typing.
Contrast. Body text and buttons meet 4.5:1; the green-on-white brand pair was chosen for it.
Motion. Carousels and announcement bars stop when you ask (prefers-reduced-motion) or press pause; nothing auto-plays sound; no flashing above 3Hz.
Stock and status dots always carry a text label next to the colour.
Touch targets are 44px or larger on phone widths, and no hover-only controls.

3. Known gaps & fix dates

We'd rather publish this table than pretend. Each row has an owner and a date; the February 2027 audit checks whether we kept them.

Gap	Where	Fix by
Product videos carry auto-captions only — accuracy is around 85%, not publishable as-is for deaf users	~40 product pages with video	31 October 2026 (human-reviewed captions)
Homepage carousel pause button is visible only on focus/hover — a screen-magnifier user can miss it	Homepage hero	30 September 2026 (always-visible control)
PDF invoices lack tagged headings, so navigation by heading fails in some readers	Invoice PDFs from order history	15 October 2026 (tagged PDF template)

4. Report a problem

Hit a barrier? Email accessibility@apexcommerce.com.au or call 1300 000 000 (8am–8pm, 7 days) and ask for the accessibility contact. Tell us the page, what you were doing, and your setup if you're comfortable sharing — we reply within 2 business days, with a human, and a fix date rather than a thank-you-for-your-feedback. Need this policy or any page in another format (large print, audio, plain-language summary)? Same address — we'll produce it within 5 business days, free.

5. How we test

Assistive tech: NVDA + Chrome and JAWS + Edge on Windows; VoiceOver + Safari on macOS and iOS; TalkBack + Chrome on Android. The checkout flow is walked end-to-end on all of them before any release that touches it.
Tools: axe automated scans in CI (zero critical/serious allowed to merge), manual keyboard walks, contrast sampling on real screenshots, and a 200%-zoom layout pass at every breakpoint.
People: two paid testers with lived experience of disability review each quarter — their findings feed the table in section 3.

6. Related documents

Terms of use — section 8 covers your Australian Consumer Law guarantees.
Privacy policy — accessibility requests never become a marketing list.
Design system & brand docs — the focus-ring, contrast and motion tokens this statement is built on.