Digital Accessibility Testing in Australia: Methods, Tools and Reporting

Define the scope and standard (usually WCAG 2.2 Level AA), run automated scans to catch common issues, then test manually: keyboard access, focus, structure, contrast, forms and errors, and key journeys with screen readers on desktop and mobile. Ideally include people with disability. Report each issue with its impact and fix, remediate by priority, and retest. No single automated test proves a site or app is accessible.

This guide is for product owners, designers, developers and testers in Australia planning or commissioning accessibility testing. It focuses on method: scoping, the testing mix, assistive technology, reporting, remediation and procurement requirements. For legal background and design guidance, see our broader guide to website accessibility in Australia.

Nothing here is legal advice. WCAG is a technical standard; obligations come from the Disability Discrimination Act, government policies and your contracts.

Accessibility testing scales with scope, so define it deliberately. W3C's Website Accessibility Conformance Evaluation Methodology (WCAG-EM) describes defining scope, exploring the site, selecting a representative sample and auditing it (W3C WCAG-EM).

Automated tools scan pages and components for rule violations: missing form labels, low colour contrast, missing alternative text attributes, invalid ARIA, duplicate IDs and empty links. Run them in development (linters and component tests), in CI, and across the live site.

Treat results as a starting point. Automated tools cannot tell whether alternative text describes the image, whether focus order is logical, whether error messages are understandable, or whether a custom component works with a screen reader. Never present an automated score as proof of accessibility.

Test key journeys with screen readers, listening for whether each element announces its name, role and state, whether headings and landmarks allow navigation, and whether dynamic changes (errors, loading, notifications) are announced.

Expert testing finds conformance issues; people with disability find whether the product actually works for them. Include participants who use different assistive technologies and approaches in usability testing of key journeys, pay them fairly, and give them time to use their own setups. See usability testing for running sessions.

Prioritise issues that block tasks for some users on key journeys, then high-impact issues in shared components (fixing a component fixes every page that uses it), then the rest. Fix in design system components and templates where possible. Retest each fix with the method that found it, including the screen reader. Track progress by journey. See accessible UI/UX design and design systems for preventing regressions.

If you sell digital products or services to government, accessibility requirements are often written into procurement. Standards Australia adopted AS EN 301 549 in 2016, and the 2020 edition references WCAG 2.1; Queensland and New South Wales procurement guidance refers to it (Queensland Government; buy.nsw). Australian Government agencies' services follow the Digital Service Standard. Read each tender for the exact standard, edition, level and reporting format required.

This example is hypothetical. A professional association is launching a member portal with sign-in, renewals, event booking and CPD records. The test scope covers those four journeys on desktop and mobile, plus the shared components. Automated scans run in CI. Manual testing finds a custom date picker that traps keyboard focus, error messages not announced to screen readers and certificates issued as untagged PDFs. Three members who use screen readers or magnification test renewals and booking. Fixes go into the shared components, PDFs are replaced with accessible HTML certificates, and the report describes partial conformance with a dated remediation plan rather than claiming full conformance.

For the legal and design context, see website accessibility in Australia and website accessibility guide. For stores, see ecommerce accessibility checklist. For AI-assisted checks, see AI software testing, which explains why they triage rather than certify.

Standards: W3C, WCAG 2.2; W3C, what's new in WCAG 2.2; W3C, WCAG-EM.

Australia: Australian Human Rights Commission, guidelines on equal access to digital goods and services; Queensland Government, buy accessible ICT; buy.nsw, government accessibility standards for ICT.

AS EN 301 549 and AHRC points were confirmed via search summaries and procurement guidance. Tables, checklists and example are ours. Nothing here is legal advice or ZSpace client data.

Accessibility testing is credible when it combines automated scans, manual checks and assistive technology testing on real journeys, reports honestly and leads to fixes in shared components. Keep WCAG, the law, guidance and contract requirements distinct, test regularly as part of delivery, and never let one automated score stand in for evidence.