Accessibility in Higher Education: Improving Digital Access for Students

Accessibility in Higher Education: improving digital access for students

Accessibility in Higher Education is about making courses, platforms and assessment usable by every student. Digital access covers learning management systems, lecture capture, PDFs, video, assessment platforms and the support services that sit behind them. This article gives a practical roadmap for UK universities and colleges to reduce barriers and meet legal and pedagogic duties.

Why accessibility matters

Students with sensory, cognitive, motor or mental-health differences must be able to access the same learning on an equal footing. When digital content is inaccessible it causes delay, extra cost and poorer outcomes. Good accessibility improves retention, academic success and compliance with institutional duties.

Legal and policy context in the UK

Two rules matter for publicly funded UK higher education providers. The Equality Act 2010 requires reasonable adjustments for disabled students. The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 require public bodies to publish accessibility statements and meet recognised technical standards. Universities should also follow guidance from funding and regulator bodies when available.

Core standards and terminology

Use these standards and terms as the baseline for procurement, audits and training.

• WCAG (Web Content Accessibility Guidelines). Aim for WCAG 2.1 AA as a minimum; WCAG 2.2 adds refinements where useful.
• WAI-ARIA roles and properties for dynamic content.
• Accessible PDF that include semantic structure, tagged headings and reading order.
• Captioning and transcripts for recorded and live audio.
• Universal Design for Learning (UDL) principles to reduce the need for individual adjustments.

Common digital barriers students face

• Poorly structured PDFs that screen readers cannot parse.
• Video without captions or with burned-in slides only.
• Complex navigation in the VLE that relies on mouse only.
• Assessment platforms that time out or lack alternative formats.
• Forms and booking systems that lack labels or error descriptions.

How to audit and fix digital access — a practical remediation workflow

This workflow is designed for a central team working with faculties and IT. It focuses on fast wins, then deeper fixes.

1. Scope: Identify core services (VLE, assessment platform, library, admin forms, lecture capture). Limit the first pass to the 100 most-used pages or 10 core course templates.
2. Automated scan: Run automated tools across scoped items to find common issues: missing alt text, poor colour contrast, empty form labels. Automation finds about 30–50% of issues quickly.
3. Manual testing: Combine keyboard-only navigation, a screen reader (NVDA or VoiceOver) and at least one mobile-device check. Focus manual effort on learning pathways and assessments.
4. Prioritise: Rank issues by impact and effort. Priorities: assessment failures, inaccessible required readings, and caption-less recorded lectures.
5. Fix iteration: Assign fixes to content owners with clear deadlines. Start with templates and components used across courses to prevent repeat work.
6. Verify: Re-test fixed items manually. Keep an issue tracker with status, owner and proof of testing.
7. Publish an accessibility statement: State current compliance, known issues and contact details for support or feedback as required by the 2018 Regulations.
8. Continuous checks: Schedule monthly automated scans and termly manual reviews of a sample of courses.

Quick remediation priorities

• Provide captions and transcripts for recordings used in assessment.
• Replace inaccessible PDFs with tagged PDFs or HTML versions.
• Ensure keyboard access for all assessment workflows.
• Fix colour contrast failures that block text legibility.

Procurement and contracts: buying accessible tools

Procurement is where many accessibility problems start. Add clear accessibility conditions to specifications and contracts.

• Require a signed accessibility conformance report against WCAG 2.1 or 2.2.
• Ask for evidence: recent independent audit results and remediation plans.
• Include acceptance tests and a warranty period for accessibility issues discovered after delivery.
• Build payment milestones around accessibility deliverables for major platforms.

Procurement checklist (practical)

• List supported accessibility standards and testing tools used by the vendor.
• Request sample course pages or a sandbox for hands-on testing with keyboard and screen reader.
• Mandate accessible documentation and training for staff and students.
• Define default configuration that preserves accessibility on deployment.

Teaching, assessment and adjustments

Accessibility must reach assessment. Tests and exams are high risk. Plan adjustments and reasonable adjustments proactively.

• Design assessments that have multiple means of engagement and response where possible.
• Provide alternative formats on request with a defined turnaround time.
• Avoid locked, time-limited online assessments unless accessibility checks are completed and adjustments are available.
• Record and publish lecture materials to the VLE with captions and slide text as searchable HTML where possible.

Assistive technology and student support

Many students use assistive technology. Support teams should be ready to advise and troubleshoot common tools.

• Common screen readers: NVDA, JAWS, VoiceOver.
• Common magnifiers and browser zoom features.
• Speech-to-text and notetaking software supported through Disabled Students’ Allowances (DSAs) where eligible.
• Library staff trained to provide accessible reading lists and alternative formats.

Training, roles and governance

Accessibility is cross-functional. Establish clear roles and a training plan.

• Senior sponsor: a lead with budget authority, often PVC or director level.
• Core delivery team: accessibility adviser, digital accessibility lead, legal/DSA liaison, and an LMS administrator.
• Faculty champions: staff who apply accessibility practice within schools and programmes.
• Mandatory training: short online modules for all teaching staff and deeper workshops for content creators and developers.

Monitoring, KPIs and reporting

Measure progress with a small set of meaningful KPIs and publish results.

• Percentage of core course templates meeting WCAG 2.1 AA.
• Average time to resolve reported accessibility issues.
• Number of staff trained in accessible content creation each term.
• Student satisfaction scores for digital learning accessibility.

Technical quick checklist for content creators

• Use semantic headings in HTML and tagged headings in Word/PDF.
• Add descriptive alt text to images used for information.
• Provide captions and a short transcript for videos.
• Ensure interactive elements are reachable by keyboard and have visible focus states.
• Label form fields and provide clear inline error messages.
• Use plain language and break long pages into smaller sections.

Two areas many institutions miss (information gain)

1. An actionable remediation cadence

Institutions often audit once and then shelve results. Instead, run three-month remediation sprints. Each sprint should fix the top 10 cross-course template issues and close all high-impact assessment failures. This keeps fixes visible, spreads cost and reduces risk before exam seasons.

2. Contractual acceptance tests for accessibility

Many contracts promise accessibility but lack acceptance tests. Include a practical test script in contracts: open a sample module, perform keyboard-only enrolment, run a screen reader through a required reading and submit a timed quiz using assistive settings. Require remediation within a fixed window if the vendor fails the test.

How to start this term (practical next steps)

1. Run an automated scan of core systems this week to map quick wins.
2. Pick one high-impact course template and apply fixes over two weeks.
3. Update procurement templates to include accessibility acceptance tests before the next tender.
4. Publish or update your accessibility statement and a clear contact route for students.

Further reading and resources

Use WCAG and WAI documentation for technical detail and the government guidance on public sector accessibility for compliance steps. Local disability services and library accessibility teams are vital partners in delivery.

Final note

Accessibility in higher education is an ongoing programme, not a one-off project. Prioritise assessments and core learning pathways first, then scale fixes across templates and platforms. Small, steady improvements reduce risk and make learning fairer for every student.