Accessibility review — AU (WCAG AA)

Comprehensive accessibility audits, remediation guidance and testing for Australian websites and mobile apps — aligned to WCAG 2.1 AA and local best practices.

  • Audit type: Automated + manual + assistive tech testing
  • Deliverables: Findings report, prioritized fixes, test scripts
  • Outcome: Improved inclusivity, reduced legal risk, better UX
Illustration of accessibility testing

Our approach

  1. Scoping: Define pages, components, platforms and assistive tech to test.
  2. Automated scan: Baseline with tools for broad coverage.
  3. Manual review: Keyboard, screen reader, zoom and contrast checks.
  4. Reporting: Prioritized remediation with code-level guidance.
  5. Validation: Re-test after fixes and deliver final certificate.
Team performing accessibility audit

Audit scope & sample checklist

Typical coverage for a WCAG AA review:

AreaWhat we checkExample fixes
PerceivableContrast, alt text, resize/zoom, captionsImprove contrast, add alt attributes, provide captions
OperableKeyboard access, focus order, skip linksKeyboard-friendly controls, visible focus states
UnderstandableClear labels, consistent UI patternsLabel inputs, improve form validation messaging
RobustSemantic HTML, ARIA where neededUse proper landmarks, correct ARIA roles

Deliverables & Australian context

Our reports are tailored to Australian organisations and reference WCAG 2.1 AA, the Disability Discrimination Act (DDA) considerations and procurement accessibility expectations common in government and enterprise engagements.

  • Executive summary for stakeholders
  • Prioritised remediation backlog (P0–P2)
  • Developer guidance with code snippets
  • Assistive tech test logs (JAWS, NVDA, VoiceOver)
  • Final validation checklist and certificate
Lead accessibility consultant face photo
Alex Morgan
Lead Accessibility Consultant

Case studies

Case study 1 — government portal
Government portal — improved navigation

Reduced keyboard traps and improved headings structure.

Case study 2 — e-commerce
E‑commerce — checkout accessibility

Fixes for form labels, error handling and ARIA live regions.

Case study 3 — education platform
Education platform — captioning & contrast

Video captions, contrast enhancements and keyboard controls.

Tools & methods

Automated scanners

Axe, Lighthouse, WAVE for broad issue detection.

Manual testing

Keyboard, VoiceOver, NVDA, JAWS and mobile assistive tech.

Developer-ready fixes

Pull‑request friendly remediation and regression checks.

Frequently asked questions

WCAG AA addresses a broad set of accessibility requirements including contrast, keyboard access, predictable navigation, and many other success criteria that balance practicality and usability for most users.

Small sites (10–20 pages) typically take 1–2 weeks. Larger platforms depend on scope and integrations; we provide a tailored timeline during scoping.

Yes — we can pair with your developers to implement fixes, produce component-level patches, and validate changes before final sign-off.

Ready to reduce accessibility risk and improve UX?

Contact our team to schedule a scoping call or request a sample report tailored to your product.