Accessibility is not just a compliance requirement for government; it is fundamental to inclusion, equity, and good digital service design. In Australia, accessibility obligations are underpinned by the Disability Discrimination Act (DDA) and reinforced through standards, policies, and procurement requirements.
One of the most important of these is Accessibility Standard AS EN 301 549, which Australian Government agencies must conform to. For digital teams delivering Drupal websites, understanding how this standard works in practice is essential.
What is the Accessibility Standard AS EN 301 549?
AS EN 301 549 is the Australian adoption of the European accessibility standard EN 301 549. It defines accessibility requirements for:
- Websites and web applications
- Mobile applications
- Documents and multimedia
- Software and ICT products
- Digital services used by the public and staff
The standard is designed to ensure people with disabilities, including vision, hearing, cognitive, motor, and neurological impairments, can perceive, understand, navigate, and interact with digital services.
Relationship to WCAG
At its core, AS EN 301 549 is built on the Web Content Accessibility Guidelines (WCAG):
- WCAG 2.1 Level AA is the primary benchmark referenced
- Requirements are mapped directly to WCAG success criteria.
- Additional obligations extend beyond websites to documents, software, and non-web ICT.
In practice, if a website meets WCAG 2.1 AA, it is well aligned with the web-specific requirements of AS EN 301 549.
How AS EN 301 549 has been adopted in Australia
Australia formally adopted AS EN 301 549:2020 through Standards Australia, aligning local requirements with international best practice.
Across government, the standard is supported by:
- The Disability Discrimination Act 1992 (Cth)
- Australian Human Rights Commission (AHRC)
- Federal, state, and territory digital and procurement policies
Australian Government context
For Australian Government agencies:
- Accessibility is mandatory for public-facing digital services.
- Conformance to AS EN 301 549, including suppliers' contractual compliance, is required in ICT and digital procurement.
- Suppliers must explicitly assert compliance in contracts.
- Agencies remain accountable for the ongoing accessibility of their sites.
This makes accessibility a shared responsibility between site owners and delivery partners.
Obligations for site owners (Australian Government agencies)
For government website owners, AS EN 301 549 introduces clear and ongoing obligations:
- Design and content must be accessible from the outset.
- WCAG 2.1 AA conformance must be achieved and maintained.
- PDFs, documents, and multimedia must be accessible.
- Third-party integrations must not introduce accessibility barriers.
- Regular testing and remediation must occur over the life of the site.
- Accessibility statements and feedback mechanisms should be provided.
Accessibility is not a one-off milestone; it is an ongoing operational responsibility. As such, accessibility needs to be considered at each phase of a project, from inception through to delivery and maintenance.
Obligations for suppliers and delivery partners
Suppliers delivering digital services to the Australian Government, including web agencies, are expected to:
- Design and build solutions that conform to AS EN 301 549.
- Follow WCAG-aligned design and development practices.
- Ensure components, themes, and templates are accessible by default.
- Provide guidance and documentation to support accessible content authoring.
- Identify and manage accessibility risks early.
- Support testing, remediation, and continuous improvement
Critically, suppliers must be able to assert conformance to the standard as part of contractual arrangements.
How AS EN 301 549 applies to Drupal website builds
Drupal is well-suited to meeting accessibility requirements when implemented correctly.
Drupal’s accessibility strengths
- Accessibility is a core principle of Drupal.
- Semantic HTML and ARIA support out of the box.
- Strong keyboard navigation and screen reader support.
- A mature ecosystem of accessible themes and modules.
What still requires care
Meeting AS EN 301 549 is not automatic. Drupal builds must account for:
- Accessible theming and component libraries.
- Correct use of headings, landmarks, and labels.
- Accessible forms and error handling.
- Colour contrast and responsive layouts.
- Media captions, transcripts, and alt text.
- PDF and document workflows.
- Editor experience and content governance.
Accessibility is as much about process and governance as it is about technology.
How Morpht ensures accessibility is covered
At Morpht, we combine deep Drupal expertise with a strong understanding of accessibility standards, WCAG, and government requirements, helping our clients deliver digital services that are compliant, inclusive, and fit for purpose.
Our approach includes:
- Accessibility-first design aligned to WCAG 2.1 AA.
- Drupal architectures that support AS EN 301 549 requirements.
- Use of proven, accessible themes and component libraries.
- Accessibility is considered in content models and authoring workflows.
- Quality assurance processes that include accessibility checks.
- Experience delivering GovCMS and complex government platforms.
We understand the contractual and policy obligations Australian Government agencies operate under, and we design solutions that enable our clients to confidently assert compliance.
Accessibility is not treated as an add-on or a final checklist; it is part of how we deliver inclusive, sustainable digital services.
Conclusion
AS EN 301 549 plays a critical role in ensuring digital services are accessible, inclusive, and usable by everyone, including people with disabilities.
The Australian Government sets clear expectations for both site owners and suppliers. For Drupal projects, it reinforces the importance of accessible design, development, and governance across the full lifecycle of a website.
