WCAG 2.2 AA conformance posture for ryderai.com.au — what works, what's pending, and how to report a barrier.
ryderai.com.au targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the conformance level Australian Commonwealth procurement, APRA-regulated entity vendor onboarding, and AHPRA-aligned clinical workflows increasingly require.
The standard covers four principles: content must be perceivable, operable, understandable, and robust. The site's design baseline targets all four, with the gaps below tracked on a remediation cadence.
Partially conformant with WCAG 2.2 Level AA at the time of last review. The site passes automated tooling for: semantic heading hierarchy, alt text on content images, keyboard navigability of every interactive element, visible focus-ring on every focusable surface, sufficient colour contrast for text against background, dark-mode-stable colour palette, and Skip-to-main-content link on every route.
prefers-reduced-motion globally via the layout-level MotionConfig, but the slide-1 to slide-2 hero transition retains a brief opacity cross-fade. Users with prefers-reduced-motion: reduceset in their OS will see the cross-fade complete in <200ms.alt for consistency with the hero variant, even though the H2 title sits adjacent. Screen readers may announce both. The page remains operable; the redundancy is intentional pending an aria-hidden wrapper.Gaps are reviewed quarterly. Critical accessibility regressions are treated as production incidents (same-session fix); non-critical issues land on the next scheduled deploy.
HTML5 + ARIA (semantic landmarks, role attributes where supported), CSS3 (responsive layout, prefers-reduced-motion respect, dark-mode colour scheme), JavaScript (Next.js 16 with server-side rendering + progressive enhancement — the page renders meaningful content without JavaScript). The site is operable with JavaScript disabled for content reading; some interactive carousels degrade gracefully to static slide-1 content via the SSR fallback.
If you encounter content that doesn't work for assistive technology you rely on, please tell us. We treat accessibility reports as production incidents.
Email: [email protected]
Include: the page URL, the assistive technology you were using (screen reader + version, voice control, switch, etc.), and what specifically didn't work. We aim to acknowledge accessibility reports within one business day.