Understanding Accessibility Review in Learning Environments

Before any review begins, it is essential to understand the learning environment, the learner population, and the institutional context. What types of content are in scope — web pages, LMS courses, documents, multimedia, assessments, interactive tools? Which platforms and systems are involved? Who are the learners, and what is already known about the barriers they face?

Scoping establishes a shared understanding of what "accessible" means in this specific context and what a realistic level of review looks like given available time and resources. This stage shapes the relevance and usefulness of everything that follows.

What this stage produces

• Shared documentation of scope and review boundaries
• Learner population context, including known barriers and assistive technology use
• Prioritised list of content and systems for review

Barrier analysis looks across four dimensions — physical and motor, cognitive, sensory, and situational — to identify where learners encounter obstacles. A key distinction is between minor friction and task-blocking barriers: not all issues carry equal weight, and effective review prioritises those that most significantly affect access.

Equally important is locating where the barrier lives. Barriers in content are addressed through remediation. Barriers in technology platforms require vendor engagement or platform changes. Barriers in workflows or institutional policy require structural responses that no individual designer can implement alone. Content-focused audits often miss the latter two categories.

What this stage produces

• Categorised barrier inventory by type and severity
• Clear distinction between access blockers and usability friction
• Identification of workflow and policy-level barriers alongside content issues

Automated tools — such as Axe, IBM Equal Access Checker, and browser-based accessibility checkers — can rapidly detect a subset of accessibility issues: missing alternative text, insufficient heading structure, colour contrast failures, and ARIA implementation errors. They are a useful and efficient starting point.

Manual testing using assistive technologies — including screen readers such as NVDA, JAWS, and VoiceOver, keyboard-only navigation, and magnification tools — is essential for capturing issues that require human judgement. A result of "no automated errors detected" does not mean a page or course is accessible. Results should always be interpreted in context, not simply reported as pass or fail.

What this stage produces

• WCAG compliance mapping by criterion and content type
• Screen reader and keyboard navigation findings
• Colour contrast, visual structure, and readability analysis
• Documentation of issues requiring manual verification

Engaging learners with disabilities in structured evaluation surfaces the gap between "technically compliant" and "actually usable." This includes heuristic evaluation against established accessibility guidelines, task-based usability testing with participants who use assistive technologies, and systematic documentation and analysis of user feedback. Small, focused tests that examine specific tasks or interface elements typically yield more actionable insights than large, undifferentiated studies.

What this stage produces

• Task completion analysis and friction mapping
• Heuristic evaluation findings from disability-centered perspectives
• Documented user feedback with analysis
• Identification of usability gaps not captured by technical audit

A technically accessible course can still exclude learners if its learning design is inflexible or its assessments assume a narrow range of abilities. This stage evaluates whether the learning experience offers genuine multiple means across all three UDL dimensions: Engagement (the why of learning), Representation (the what), and Action and Expression (the how).

It also assesses whether assessment tasks are designed equitably — whether the format of assessment is measuring the intended learning outcome, or inadvertently measuring a learner's ability to perform under conditions unrelated to that outcome.

What this stage produces

• UDL alignment map across all three dimensions
• Assessment equity analysis identifying format-based barriers
• Recommendations for flexible pathways and varied representation
• Identification of where inflexibility creates barriers for specific learner groups

Findings are only useful if they can be acted on. Effective reporting translates technical and learning design findings into a prioritised remediation roadmap — distinguishing quick wins from longer-term structural changes, and connecting recommendations to real governance, workflow, and procurement contexts.

Reports should serve multiple audiences with different needs. Technical teams need specific, reproducible guidance. Learning designers need design principles and concrete alternatives. Leadership needs strategic framing, risk context, and understanding of what systemic changes are required. A single report that attempts to serve all three audiences typically serves none of them well.

What this stage produces

• Prioritised remediation roadmap with effort and impact framing
• Differentiated outputs for technical, design, and leadership audiences
• Connection of findings to governance, policy, and procurement contexts
• Framework for continuous improvement, not one-time remediation