Run WPHC
Accessibility standards guides
AustraliaLast reviewed:

DDA Australia Digital Accessibility Readiness Guide

DDA Australia readiness planning uses practical accessibility checks to help reduce digital barriers before manual review.

This guide is for general accessibility-readiness planning. It is not legal advice, a certification, or a substitute for manual accessibility and compliance review.

Who this may apply to

  • Australian public websites and customer portals
  • Digital goods, services, and information experiences
  • Organizations planning accessibility remediation
  • Teams preparing manual accessibility review across key journeys

WCAG relationship

Australian digital accessibility guidance commonly uses WCAG-aligned review methods to identify barriers, while DDA context and obligations need separate review.

What the readiness check can surface

  • Missing labels and instructions in forms
  • Image alternative and link-purpose gaps
  • Keyboard and focus-readiness signals
  • Heading, landmark, and content-structure issues
  • Contrast and mobile interaction signals

What still needs manual review

  • Complete task testing with assistive technologies
  • Whether specific services or content are in scope
  • PDF, media, and third-party content review
  • User-journey review for real customer scenarios

Common readiness issues

Forms that do not clearly describe inputs or errors

Navigation and filters that need keyboard testing

Mobile controls that are too small or crowded

Images or icons without meaningful text alternatives

Content order that becomes confusing on smaller screens

Official sources

FAQ

How does WCAG relate to DDA Australia planning?

WCAG-aligned checks are commonly used to identify digital barriers, but DDA scope and formal interpretation require separate review.

Can WARC assess DDA obligations?

No. WARC surfaces website readiness signals and helps teams prepare for manual accessibility and compliance review.

Which issues are useful to check first?

Start with forms, navigation, keyboard access, text alternatives, contrast, and mobile interaction because these often affect practical access.

Why include manual review after a scan?

Manual review confirms real task completion, assistive-technology behavior, and context that automated checks cannot determine.

Related standards

Start with the Website Accessibility Readiness Check

Scan a public URL to find practical accessibility, usability, forms, navigation, and mobile interaction signals before planning manual review.

Run the Website Accessibility Readiness Check