Skip to main content
Back to Blog
Faculty Resources2 min read

Evaluating Publisher Materials for Accessibility at Australian Universities

Assess the exact publisher platform, edition and assigned material. Request usable sources and alternatives, document barriers and coordinate timely student access.

Aelira Team•Updated on
Share:LinkedInX

Publisher materials vary by platform, edition and resource. Do not assume every product from Pearson, Cengage, Wiley or another publisher has the same accessibility status. Evaluate the actual resources students must use and the relevant conformance evidence.

Inventory the assigned material

Include slides, readings, interactive exercises, assessments, test banks and media. Record the product, edition, platform, file type, student task and observed barrier. Test the institution's actual access path and roles rather than the publisher's homepage alone.

Request evidence and usable alternatives

Ask the institutional representative or publisher's current accessibility contact for an ACR where relevant, supported assistive technologies, known limitations, accessible source files and a correction timetable. Confirm the version and evaluation date behind any report. A marketing commitment is not evidence that a particular file is usable.

The institution can send a request identifying the resource and edition, describing the barrier, specifying the format or task needed, and stating the date students require access. The request should be factual and based on testing; avoid attributing unverified experiences to anonymous faculty.

Coordinate interim access

Work with disability services, library and learning-design teams on timely access. Consider another licensed source, an accessible edition or an appropriately evaluated alternative. Check copyright and licensing before modifying or redistributing publisher content. A blanket statement that any alternative format resolves the institution's obligations is unsafe.

Review remediation candidates

Inspect source structure, tables, reading order and generated descriptions. Review captions against the actual audio and necessary sounds rather than applying a universal accuracy percentage. Some complex material needs specialist work or replacement.

Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.

Build requirements into selection

Document accessibility requirements, evidence, delivery dates and correction responsibilities in the actual contract. The DDA and DSE framework requires an Australian assessment of education on the same basis, consultation and reasonable adjustments. It does not adopt the US Title II dates or prescribe a WCAG version itself. The availability of automation does not establish whether unjustifiable hardship applies.

Retain requests, testing and response records under institutional controls. Those records support management and review; they do not guarantee a legal outcome or substitute for usable material.

Aelira Team

Aelira Team

•Accessibility Engineers

The Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.

Explore accessibility remediation with Aelira

Join the pilot to evaluate Aelira's beta workflows. Support varies by format; outputs can be partial and need human review.