Accessibility Statement

Last updated: 1 May 2026.

OzCoWilliams is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We aim to comply with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

What we do

  • Maintain semantic HTML structure (one H1 per page, logical heading hierarchy, landmarks).
  • Provide meaningful alt text for content images and aria-labels for icon-only buttons.
  • Ensure colour contrast meets WCAG AA (4.5:1 for body text, 3:1 for large text).
  • Test keyboard navigation across all primary user flows (skip-to-content, form completion, navigation).
  • Set prefers-reduced-motion respect on animated elements (cloud overlay, scroll-reveal).
  • Use real anchor and button elements (not styled divs) so screen readers announce roles correctly.
  • Lazy-load images while ensuring above-the-fold content remains synchronously rendered.

Known limitations

The following areas have known accessibility shortfalls inherited from the visual-replica build mandate. These are tracked and will be addressed in the post-launch CRO/UX sprint:

  • Brand-green outline button: the secondary CTA on the homepage hero quotes section uses brand colour #2B884D on white, which measures 4.38:1 against the WCAG AA threshold of 4.5:1. The button is fully keyboard-focusable and screen-reader-readable; only the colour-contrast metric is marginally below threshold.
  • Testimonial-pagination dots: 8 px diameter, below WCAG 2.1 AAA target-size guidance (44 px). Each dot has an aria-label and is keyboard-operable; visible size matches the live design.

Assistive-tech compatibility tested

  • NVDA + Firefox (Windows)
  • VoiceOver + Safari (macOS, iOS)
  • TalkBack + Chrome (Android)
  • Keyboard-only navigation (Tab / Shift-Tab / Enter / Esc)

Tooling we use

Every dev deploy runs Lighthouse CI; the production deploy fails if accessibility drops below 90/100. We also run periodic manual checks via axe DevTools, Wave, and screen-reader testing.

Report an accessibility issue

If you encounter an accessibility barrier on this site, please tell us — we treat these reports as priority bugs. Include the page URL, the assistive technology you were using, and a description of the issue.

Standards reference