What Is AS EN 301 549?

AS EN 301 549 is Australia's adoption of the European standard EN 301 549, which sets out accessibility requirements for information and communications technology (ICT) products and services. Published by Standards Australia, it provides a comprehensive framework that goes well beyond web content, covering software, hardware, documentation, and support services. For Australian universities, it represents the most detailed technical benchmark available for ensuring that the technology you procure, build, and deploy is accessible to people with disabilities.

From Europe to Australia: The Origin of the Standard

EN 301 549 was originally developed by the European Telecommunications Standards Institute (ETSI) to support EU public procurement directives. The European standard needed a way to define, in precise technical terms, what "accessible ICT" actually means. The result was a document that maps accessibility requirements across every category of technology — from websites and mobile apps to self-service kiosks, telecommunications equipment, and electronic documents.

Standards Australia adopted this European standard with the "AS" prefix, signalling its recognition as an Australian national standard. The content is functionally identical to the European source document, which means Australian institutions benefit from a standard that has been rigorously developed, widely tested, and internationally recognised.

More Than Web Accessibility: The Full Scope

One of the most common misconceptions about accessibility standards is that they only apply to websites. AS EN 301 549 deliberately corrects this. The standard covers:

• Web content (through direct reference to WCAG)
• Non-web software, including desktop and mobile applications
• Hardware, such as computers, kiosks, and AV equipment
• Electronic documents, including PDFs, Word files, and spreadsheets
• Authoring tools used to create content
• Support services and documentation, including help desks and user guides
• Real-time communication tools, such as video conferencing platforms

For a university, this breadth matters. Your institution does not just run a website. You deploy learning management systems, distribute lecture recordings, provide self-service enrolment kiosks, offer IT help desks, and produce thousands of documents each semester. AS EN 301 549 provides requirements for all of these.

The WCAG Connection

At its core, AS EN 301 549 incorporates WCAG 2.1 Level AA as the baseline for web content and non-web software where applicable. Chapter 9 of the standard maps directly to WCAG 2.1 success criteria for web content, while Chapters 10 and 11 extend similar principles to non-web documents and software.

This means that if you are already working toward WCAG 2.1 compliance, you are addressing a significant portion of AS EN 301 549. However, the standard goes further. It includes requirements that WCAG does not cover — for example, requirements around closed functionality (where assistive technology cannot be installed), biometric identification, and real-time text communication.

Understanding this relationship is important: WCAG tells you how to make web content accessible, while AS EN 301 549 tells you how to make your entire ICT environment accessible. The two are complementary, not interchangeable.

How It Applies to Australian Universities

Australian universities operate under the Disability Discrimination Act 1992 (DDA) and the Disability Standards for Education 2005 (DSE). Both require that students with disabilities can access education on the same basis as other students. Neither statute prescribes a specific technical standard — they establish legal obligations without detailing exactly how to meet them.

This is where AS EN 301 549 fills a critical gap. While it is not directly mandated by the DDA or DSE, it serves as the most authoritative technical reference for demonstrating compliance. If a student lodges a complaint about an inaccessible learning platform or an unreadable PDF, the question becomes: did the university take reasonable steps to ensure accessibility? Adherence to a recognised standard like AS EN 301 549 provides strong evidence that you did.

For institutions navigating Australian accessibility requirements, the standard also has practical value in procurement. When evaluating new software platforms, hardware, or digital services, referencing AS EN 301 549 in your procurement criteria gives vendors a clear, measurable benchmark. Instead of asking whether a product is "accessible," you can ask whether it conforms to specific clauses of the standard.

Practical Steps for Higher Education

Adopting AS EN 301 549 does not require overhauling everything at once. A practical approach for universities includes:

1. Use it as a procurement filter. Require vendors to provide accessibility conformance reports mapped to AS EN 301 549 or its European equivalent.
2. Audit your document pipeline. PDFs and office documents fall under the standard's scope. Understanding whether WCAG applies to your PDFs is a good starting point.
3. Assess your LMS and key platforms. Apply the standard's software requirements to the tools students use most.
4. Train procurement and IT staff. Familiarity with the standard helps teams ask the right questions before contracts are signed.
5. Document your efforts. Compliance is not binary. Demonstrating a systematic approach to meeting the standard strengthens your position under the DDA and DSE.

Building Toward Compliance

AS EN 301 549 gives Australian universities a technically rigorous, internationally aligned framework for ICT accessibility. It bridges the gap between legal obligations and practical implementation, covering the full range of technology that students and staff interact with daily.

Aelira helps Australian universities put standards like AS EN 301 549 into practice — from scanning and remediating documents at scale to providing the compliance evidence you need. If your institution is working toward a more accessible ICT environment, get in touch to see how we can help.