Website accessibility is both a moral requirement and a business requirement. People should not be excluded from information or services because of the way they navigate, read, hear, understand or interact. Organisations should also ask a blunt commercial question: what does excluding one paying customer cost?
This resource centre brings together DDSN's practical guidance on website accessibility standards, WCAG 2.2, content production, testing, remediation and ongoing assurance. It is written for IT managers, digital leaders, communications teams, website authors and people responsible for government and education services.
Explore DDSN website accessibility services
Start with website accessibility standards
If you are responsible for improving an existing website, begin with the standard and the operating process behind it. Accessibility is not a one-time design check or a report that sits outside normal publishing. It requires a repeating cycle of measurement, prioritisation, repair, retesting and prevention.
Our main implementation guide explains WCAG conformance levels, Australian requirements, the moral and business case, platform selection, organisational responsibilities and the practical steps needed to begin an accessibility improvement program.
For organisations ready to move from reading to action, see how DDSN assesses, repairs, reports on and maintains website accessibility.
Understand WCAG 2.2 and accessibility assurance
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines. It provides testable success criteria, but a scanner score is not the same as conformance. Reliable assurance combines automated testing with expert review, keyboard testing, assistive-technology checks and clear documentation of scope and limitations.
A practical explanation of the new requirements affecting keyboard focus, dragging interactions, target sizes, help, repeated entry and accessible authentication—and what digital teams need to change.
An accessibility statement is valuable only when it accurately reflects testing, known limitations, alternative ways to access services and a real repair process. This guide explains how public claims can run ahead of the evidence behind them.
Compare DDSN's levels of scanning, reporting, remediation, author support and content assurance.
Build an ongoing accessibility process
Websites change. New pages, components, documents and campaigns can introduce barriers after an audit is complete. Ongoing accessibility depends on finding issues early, fixing the source of repeated defects and improving the way new material is produced.
Learn how ongoing monitoring, remediation, reporting and training differ from a point-in-time audit—and why accessibility needs an operating model rather than a finish date.
A data-led guide to the issues accessibility scans repeatedly find, how to distinguish content faults from component faults, and where remediation effort is best spent first.
PDFs and office documents often sit outside website governance even though users experience them as part of the same service. This guide covers inventory, ownership, remediation and when HTML is the better publishing choice.
Accessibility is one part of keeping a digital platform useful. DDSN's continuous improvement service combines planned development, technical support, measurement, optimisation and platform health.
Create accessible content
Developers cannot maintain website accessibility alone. Authors make daily decisions about headings, links, alternative text, tables, images, documents and video. Clear publishing controls and practical training prevent defects before they enter the repair queue.
A practical guide for people creating and publishing website content, including author responsibilities, testing tools and a pre-publication accessibility checklist.
How to use colour, labels, captions, tables, alternative text and supporting explanations so that charts and figures communicate their meaning to more people.
Extend accessible authoring beyond the CMS by giving documents an appropriate structure, reading order, language, link text and text alternatives—or replacing them with accessible HTML where possible.
See accessibility engineering in practice
Accessibility evidence is strongest when it is built into real delivery: design decisions that constrain unsafe combinations, structured content that retains metadata, migration checks that preserve alternative text, and human review before publication.
See how DDSN approached a high-volume education website whose value depends on findability, structured course information, accessible content and a platform that supports continuous improvement.
During Hearing Australia's accelerated migration, DDSN rebuilt 297 pages, audited 617 source URLs, verified metadata and alternative text, and saved every migrated page for human review before publication.