Skip to table of contents

Understanding Accessibility Review in Learning Environments

A guide to the knowledge foundations, methodology, key decisions, and learner outcomes that characterise effective accessibility review.

Screen reader and keyboard-optimised version. This is a fully linear, plain-structure version of this resource designed for use with assistive technologies. All content is presented in reading order with no tabs, accordions, or JavaScript. An interactive version with tabs and expandable sections is also available.

Knowledge Foundations

Effective accessibility review draws on four interconnected bodies of knowledge. The most rigorous reviews hold all four in view simultaneously — and produce findings that a surface-level compliance check cannot.

The four knowledge pillars

Each pillar represents a distinct area of expertise that contributes to a complete review. In practice, they are deeply interconnected: strong barrier analysis requires disability knowledge; evaluating a learning experience requires UDL fluency; connecting findings to action requires understanding governance and law.

1. Disability and learner variability

Accessibility review begins with understanding disability as a relationship between a person and their environment — not a fixed category. This includes familiarity with major disability categories (visual, auditory, motor, cognitive, neurological, and situational), how assistive technologies work and what they require from content, and how barriers affect participation across physical, cognitive, sensory, and situational contexts. Many barriers also affect people without formal disability designations — including those with temporary impairments, older learners, or people accessing content in constrained environments.

2. Universal Design for Learning (UDL) and inclusive design

Universal Design for Learning (UDL), developed by CAST, guides the design of learning experiences to accommodate variability from the outset. It is organised around three principles:

UDL is complementary to technical accessibility standards: where WCAG addresses whether content is technically accessible, UDL addresses whether the learning experience offers all learners genuine ways to engage with and demonstrate knowledge.

3. Technical accessibility standards

The Web Content Accessibility Guidelines (WCAG), currently at versions 2.1 and 2.2, provide the technical baseline for digital accessibility across web content, LMS platforms, digital documents, multimedia, and interactive learning objects. They are organised around four principles — Perceivable, Operable, Understandable, and Robust (POUR). Standards fluency means interpreting and applying criteria in context, not simply running automated checks and reporting pass/fail results.

4. Laws, governance, and institutional context

Technical findings create lasting change only when they connect to real accountability structures. This requires understanding relevant legislation (addressed in Section 5) and also institutional governance: who has authority to require accessibility in procurement, which workflows create barriers that no individual designer can resolve, and how accessibility responsibilities are distributed across an organisation. Reviews that ignore institutional context produce findings that sit in reports without generating change.

A practical hierarchy: Use WCAG to audit the artefact. Use UDL to evaluate the learning experience. Use inclusive design principles to assess the system. Effective review holds all three lenses simultaneously and situates findings within the institutional context where they must be acted on.

What distinguishes expertise from checklist compliance

Automated tools efficiently detect a meaningful subset of issues — missing alternative text, insufficient heading structure, colour contrast failures, and ARIA errors — but can identify only approximately 30–40% of real accessibility barriers. They cannot assess whether a learning experience is equitably designed, whether assessment tasks assume a narrow range of abilities, or whether the barriers most affecting a specific learner population have been addressed. The gap between "technically passes" and "actually works for learners" is where human expertise is irreplaceable.

Accommodation versus design: an important distinction

Accommodation addresses a specific learner's access need after the fact. Accessible design anticipates learner variability from the outset, building flexibility into the learning experience itself. The two are complementary: accommodation remains necessary for some learners in some situations, but organisations that rely on it as their primary accessibility strategy are managing barriers rather than removing them. The purpose of accessibility review is to identify what barriers exist and where they are located — in content, technology, workflows, or institutional structures.

Methodology

Effective accessibility review is structured, iterative, and multidimensional. The six stages below represent a comprehensive approach; in practice, scope and depth vary with context, resources, and organisational need. Understanding the full methodology clarifies what is gained or lost when particular stages are abbreviated.

Stage 1

Intake and Scoping

Understanding the context before assessing it

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
Note: Findings from a review that lacks adequate scoping are often difficult to act on, because they are not connected to the actual context of the organisation.

Stage 2

Barrier Analysis

Identifying what blocks participation — and where

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 (physical, cognitive, sensory, situational) and severity
  • Clear distinction between access blockers and usability friction
  • Identification of workflow and policy-level barriers alongside content issues
Note: Barrier analysis that draws on educators, technologists, and learners with disabilities consistently produces more actionable findings than single-discipline review.

Stage 3

Technical Standards Audit

Automated and manual testing against WCAG

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

Stage 4

User-Centered Evaluation

Centering the lived experience of disabled learners

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
Note: Legal enforcement increasingly scrutinises whether users can independently complete tasks on digital platforms — not only whether technical standards are met. Experiences that pass automated checks but remain unusable with assistive technologies have been cited in accessibility complaints and settlements. Technical compliance and genuine usability are not the same thing.

Stage 5

Learning Design and UDL Assessment

Is the learning experience itself inclusive?

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
Note: Assessment equity analysis asks not only whether assessment platforms are technically accessible, but 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.

Stage 6

Reporting and Remediation Planning

Findings that can actually be acted on

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
Note: Accessibility barriers accumulate as content is created, platforms are updated, and organisational contexts change. Periodic review, embedded in ongoing practice, prevents the buildup of unresolved issues and is more effective than a single comprehensive audit conducted in isolation.

Key Decisions That Shape a Review

No two accessibility reviews look the same. The decisions an organisation makes about scope, depth, timing, and involvement determine what kind of review is appropriate and what it will produce. Understanding these dimensions helps set realistic expectations — and make better use of the review process.

Scope: what is being reviewed

  • Spot audit — a single course, module, document, or platform feature. Useful for prioritisation or addressing a known concern. Limited in what it reveals about systemic patterns.
  • Programme review — a full learning pathway or credential. Reveals patterns across content types and surfaces inconsistencies in how accessibility is applied across a curriculum.
  • Institutional review — systems, policies, and practices organisation-wide. Required to address workflow, governance, and procurement-level barriers that individual content reviews cannot reach.

Depth: how thorough the review is

  • Rapid assessment — key barriers identified efficiently, useful for initial prioritisation. Trades methodological completeness for speed. Findings should be treated as a starting point, not a complete picture.
  • Comprehensive audit — full WCAG, UDL, and user-centered evaluation across all six stages. Produces the most complete findings but requires more time and resources.
  • Ongoing review — iterative review embedded in the design and development cycle. The most effective long-term approach, as it prevents accumulation of barriers rather than addressing them retrospectively.

Learner involvement: who participates in evaluation

  • Expert review only — specialist assessment without direct user testing. Efficient and appropriate for many contexts, but misses the gap between expert prediction and actual learner experience.
  • Expert plus user testing — structured participation from learners with disabilities alongside expert review. Surfaces issues that expert review alone does not capture. Requires careful ethical and logistical planning.
  • Co-design — learners with disabilities involved in shaping remediation and redesign decisions. Produces the most learner-centered outcomes and builds genuine community trust.

Timing: when the review happens

  • Pre-development — informing design decisions before content is built. Least costly and most effective — accessibility built in from the start.
  • Pre-launch — catching issues before content goes live. More costly than pre-development review but significantly less costly than post-launch remediation.
  • Post-launch — addressing barriers in existing content. Most commonly needed but most costly to address. Often reveals the need for both content remediation and systemic change.

Focus area: what kind of review it primarily is

  • Digital content — web pages, LMS content, documents, multimedia, and assessments. The most common starting point for accessibility review in educational settings.
  • Learning design — UDL alignment, assessment equity, and the overall flexibility of the learning experience. Extends beyond technical compliance to equity in learning design.
  • Systems and governance — institutional policy, procurement practices, and organisational workflows. Required for systemic and sustainable change.
Rapid vs. comprehensive approaches: Rapid assessments trade methodological completeness for speed. They are useful for initial prioritisation, particularly when resources are constrained, provided findings are understood as a starting point rather than a complete picture of the accessibility landscape.

Learner Impact

Accessibility review creates change at two different horizons. The shorter-term outcomes are tangible and measurable. The longer-term shift is cultural — and has a broader effect on how an organisation designs and delivers learning for everyone.

Shorter-term outcomes: what becomes visible and fixable

Outcomes typically achievable within the review cycle and immediate remediation period

Outcome What this looks like in practice
Barriers are named and prioritised
A clear picture of what is blocking learners, organised by severity and remediation effort.
Teams move from vague awareness of "accessibility issues" to a specific, actionable inventory they can work through systematically.
Immediate issues are remediated
Common barriers — missing captions, poor contrast, absent alternative text, inaccessible documents — addressed once identified.
Many high-impact, low-effort fixes are implemented quickly. Learners who were previously excluded gain access to content they were being denied.
Compliance is documented
A formal review and remediation roadmap provide evidence of due diligence for regulatory and governance purposes.
Organisations can demonstrate to regulatory bodies, leadership, and learners that they are taking accessibility obligations seriously and acting on them.
Team knowledge grows
Designers, developers, and faculty develop practical accessibility literacy through engagement with the review process.
The review itself becomes a capacity-building experience. Teams emerge better equipped to identify and address issues in future work.

Longer-term change: what becomes embedded in practice

Outcomes that develop over repeated review cycles and sustained organisational commitment

Outcome What this looks like in practice
Accessibility becomes a design habit
Rather than a retrofit, accessible design is incorporated from the beginning of content development.
Future remediation costs decrease significantly. Designers stop asking "is this accessible?" at the end of a project and start making accessibility-informed decisions throughout.
All learners benefit
Better structure, clearer language, flexible formats, and consistent navigation improve the experience for every learner.
Features designed for learners with disabilities improve usability, comprehension, and engagement for the whole cohort.
Institutional culture shifts
The focus moves from individual accommodation toward proactive inclusion — affecting procurement, faculty development, and organisational identity.
Accessibility stops being "someone else's job" and becomes a shared expectation embedded in how the organisation hires, trains, procures, and governs.
Governance and procurement improve
Organisations develop the literacy to require and evaluate accessibility in vendor contracts and new platform selection.
Accessibility requirements appear in RFPs. Platform evaluations include assistive technology testing. Vendors are held to explicit standards as a condition of partnership.
On evidence and outcomes: Research consistently demonstrates that accessibility improvements support retention, participation, and equity beyond compliance. Inclusive design produces better learning environments for all learners — a case that complements, and often exceeds, the legal argument for accessibility investment.

Organisational Reflection

The questions below are designed to help you think through your organisation's current relationship with accessibility. They are not a formal assessment — there are no scores or categories. They are intended to surface useful questions and help identify where the most productive focus may be for your context. Working through them with colleagues across different roles often yields more complete and honest responses.

On your current knowledge of barriers

  • What do you actually know about the accessibility barriers your learners currently face? How did you find out, and how confident are you in that picture?
  • Are there learner groups whose accessibility experience you know relatively little about? What would it take to understand it better?
  • Where in your organisation do accessibility barriers most likely go unreported — and why?

On your design and development practice

  • At what point in your content development process does accessibility currently get considered? What happens as a result of that consideration?
  • Where does accessibility get dropped — at the point of production, during review, or in the handoff between teams? What does that tell you about where the gap is?
  • Are the people responsible for accessibility in your organisation supported with the time, tools, and authority they need to do the work well?

On institutional structures and governance

  • Does your organisation have documented accessibility policies or an accessibility plan? If so, how connected are they to day-to-day practice?
  • Where does accessibility still get treated as someone else's responsibility — in procurement decisions, vendor evaluation, curriculum governance, or platform selection?
  • What would need to change — structurally, not just culturally — for accessibility to be consistently embedded in how your organisation operates?

On capacity and sustainability

  • How are you building accessibility expertise across your organisation, so progress does not depend on one or two individuals?
  • How do you know whether your accessibility efforts are actually improving outcomes for learners with disabilities? What evidence do you have, and what is missing?
  • What would a realistic next step look like for your organisation — given your current resources, constraints, and the people who have the knowledge and authority to move things forward?

Organisations that make meaningful progress on accessibility tend to be those that create space for honest conversations about where the gaps are, not where they would like them to be. The other sections of this resource are intended to provide useful context for those conversations.

Academic Citations

The following sources underpin the knowledge claims, frameworks, and evidence presented in this resource. Citations are grouped by the area of the resource they primarily support.

Technical Standards

Primary technical standard

Web Content Accessibility Guidelines (WCAG) 2.2. World Wide Web Consortium (W3C), 11 December 2024.
https://www.w3.org/TR/WCAG22/

Professional Bodies of Knowledge

Foundational concepts

IAAP CPACC Body of Knowledge. International Association of Accessibility Professionals (IAAP), October 2023.
https://www.accessibilityassociation.org/sfsites/c/resource/CPACCBoK

Technical review methodology

IAAP Web Accessibility Specialist (WAS) Body of Knowledge. International Association of Accessibility Professionals (IAAP).
https://www.accessibilityassociation.org/sfsites/c/resource/WASBoK_ePUB

Empirical Evidence and Audit Data

Large-scale audit

Freeman, Jared. "The WebAIM Million — The 2026 report on the accessibility of the top 1,000,000 home pages." WebAIM, 29 March 2026.
https://webaim.org/projects/million/

Evidence synthesis

Sauer, C., et al. "Accessibility engineering in web evaluation process." EAI Endorsed Transactions on Pervasive Health and Technology, 2023.
DOI: 10.4108/eai.26-10-2023.2337800

Higher Education — Online Learning

Online learning review

"Accessible and Inclusive Online Learning in Higher Education." ERIC (EJ1480115), 31 August 2025.
https://eric.ed.gov/?id=EJ1480115

Higher Education — Universal Design

Universal design application

Bracken, S., & Novak, K. "Universal Design for Instruction & Learning in Higher Education." ERIC.
https://files.eric.ed.gov/fulltext/EJ1435143.pdf

↑ Back to contents