Selecting a Learning Management System: Accessibility, Integration and Total Cost

Begin with institutional workflows

A learning management system should support the institution's teaching and assessment practices. Before preparing a product shortlist, describe common workflows: creating a course, enrolling learners, releasing materials, collecting assignments, providing feedback and exporting records. Include staff who perform these tasks and learners who experience the results.

Distinguish essential requirements from preferences. A small institution may need reliable course delivery and simple support more urgently than a complex analytics suite. A specialist programme may depend on a particular assessment format. Document the problem each requirement addresses so that procurement does not become a competition for the longest feature list.

Test teaching and learner experience

Ask shortlisted suppliers to demonstrate the same scenarios using representative material. Include a routine task and a difficult one, such as correcting an enrolment error or recovering an interrupted submission. Record the number of steps, clarity of messages and support needed. Let teachers and students perform tasks rather than watch a polished presentation.

Assess mobile and low-bandwidth use where relevant. Check how the system handles large files, deadlines, feedback formats and multilingual content. Determine which features require additional licences or external services. A capability shown in a demonstration should be confirmed as part of the proposed configuration and contract.

Examine accessibility in practice

W3C's WCAG provides a recognised reference for digital accessibility.^[1] Request evidence of the supplier's accessibility approach, but also test important journeys with users and assistive technologies. Check keyboard navigation, focus visibility, form labels, error messages and alternatives for media. Accessibility must extend to course content and connected tools, not only the platform's login page.

Document barriers and agree remediation responsibilities before procurement. Establish an accessible support route and a process for alternative arrangements. A statement of conformance is useful evidence, but it does not remove the need to assess the institution's actual configuration and learning materials.

Verify integrations and data flows

Identify the systems the LMS must connect with, such as identity management, student records, library services and assessment tools. 1EdTech's LTI standard supports standardised integration of learning tools with platforms.^[2] Ask which versions and services are supported and test the intended connection. A general claim of compatibility may not cover the particular workflow you need.

Map data transferred through each integration, access permissions and responsibility for errors. Review account provisioning, staff departures and student completion. Determine how records can be exported in usable formats and whether attachments, feedback and metadata are included. Test an export before committing to a long-term service.

Illustrative example: comparing two options

Imagine an institution comparing two LMS offers. One has a lower subscription price but requires separate paid services for essential assessments and manual enrolment work. The other includes these functions but has a more demanding migration process. A structured pilot reveals that both can deliver courses, while staff effort and support arrangements differ substantially.

The decision team calculates implementation, training, integration and ongoing administration costs over a common period. It records the assumptions and sensitivity to learner growth. The example does not establish which product is better; it shows why the cheapest licence may not represent the lowest institutional cost.

Plan support, continuity and exit

Agree service responsibilities, incident communication, backup arrangements and recovery expectations. Establish who supports learners outside normal teaching hours and how unresolved issues escalate. Evaluate supplier stability and the institution's ability to operate the chosen model, including any hosting responsibilities.

Include migration and exit in the plan. Specify data ownership, export assistance, retention, deletion and the treatment of materials after the contract ends. Avoid storing the only copy of essential academic records in a format the institution cannot retrieve. Review legal and privacy terms with the appropriate specialists for the jurisdictions and learners involved.

Make an evidence-based decision

Use a weighted evaluation matrix only after agreeing priorities. Record evidence and unresolved risks alongside scores, then consider whether a numerical ranking hides a non-negotiable failure. A serious accessibility or data issue should not disappear because a product scores well on cosmetic features.

Run a bounded pilot with success criteria, support arrangements and a review date. Include implementation readiness in the final recommendation: training, content migration, ownership and budget. The strongest choice is the system the institution can use effectively, support responsibly and leave safely if its needs change.