AI tools are increasingly presented as a route to more personalised and inclusive learning. For students with disabilities, however, a tool that can generate an explanation or simplify a text is not automatically accessible, safe, or educationally useful. A student may be able to receive an answer but still be unable to navigate the interface, formulate a prompt, interpret the response, or use it independently. Schools therefore need to evaluate not only what an AI system can produce, but whether a learner can meaningfully access, question, and benefit from it.
This question has become more urgent as new research has begun to focus specifically on inclusive AI. On 28 September 2026, UNESCO’s Institute for Information Technologies in Education highlighted a global study on AI, ICT, and inclusion for children with autism, ADHD, and learning disabilities. In a peer-reviewed study published in July 2026, special education teachers described both useful applications and barriers involving accessibility, privacy, bias, and training. A separate 2026 classroom study examined the support educators provided when students with disabilities used ChatGPT in science learning. Taken together, these sources suggest a practical principle: AI inclusion depends on the fit between the learner, the task, the interface, and the human support around the technology.
Why accessibility is more than an AI feature
In ordinary product demonstrations, accessibility may appear as a list of features: speech input, audio output, summarisation, image description, or simplified text. These can be valuable, but a feature is not the same as an accessible learning experience. A voice interface may not work reliably for a learner with a speech disability. A long AI-generated answer may overwhelm a student who needs information broken into smaller steps. A visual explanation may remain inaccessible to a learner who uses a screen reader. A chatbot may be technically usable while producing language that is difficult to interpret or that misrepresents a learner’s communication style.
The UNESCO IITE report draws on a literature review, expert interviews, and case studies from 22 countries. It proposes a system-level framework organised around six domains—People, Products, Pedagogy, Policy, Place, and Provision—and four cross-cutting conditions: Capacity, Co-creation, Consistency, and Conscience. Its central implication is that inclusion cannot be delivered by software alone. Educator preparation, learner participation, reliable provision, institutional policy, and the learning environment all influence whether technology supports meaningful participation.
This matters because the phrase “AI for special education” covers very different tools and needs. A speech-to-text tool, a generative chatbot, an adaptive practice system, an augmentative and alternative communication (AAC) aid, and an AI-powered image description service do not have the same purpose or risk profile. Evaluation should begin with a specific learner goal rather than a general assumption that AI will personalise learning.
What recent research actually tells us
A qualitative study by Marie Sakowicz and Foad Hamidi, published in Universal Access in the Information Society on 28 July 2026, interviewed seven special education teachers in public schools in the eastern United States. Teachers described using AI-enabled technologies for personalised learning and engagement, but also reported accessibility problems—especially for some students with speech and communication disabilities—as well as concerns about data privacy, algorithmic bias, and insufficient professional development. Because the sample was small and qualitative, the study does not estimate how common these experiences are across all schools. Its value is in making implementation barriers visible and identifying questions that broader research should test.
A peer-reviewed study by Kok-Sing Tang and colleagues, first published online on 12 May 2026, analysed educator support during ChatGPT use in an inclusive science classroom. The authors organised observed support into four domains: instructional, literacy, emotional-behavioural, and technological. In practice, this meant helping learners understand the purpose of an AI activity, formulate and interpret questions, remain engaged, and operate the technology—including using audio output or receiving help with typing where needed. The authors describe a situated classroom study, not a universal recipe; the taxonomy is best treated as a useful lens for planning and reflection, not proof that one approach works for every disability or age group.
These studies do not establish that generative AI improves academic outcomes for all learners with disabilities. They instead show why the quality of implementation deserves attention. UNESCO’s report likewise combines evidence and practice examples to identify opportunities and systemic barriers, rather than presenting a single controlled trial that proves the effectiveness of every tool. Schools should preserve this distinction between promising use cases, practitioner experience, and causal evidence of learning gains.
Eight checks before adopting AI for inclusive learning
1. Start with a learner-defined goal
Define the barrier the learner is trying to overcome. Is the goal to access written instructions, practise a concept, communicate an idea, plan a multi-step task, or demonstrate knowledge in a different format? Involve the student, family where appropriate, special educators, classroom teachers, and relevant support professionals. Avoid treating a diagnosis as a complete description of a learner’s preferences or abilities. Two students with the same diagnosis may need different supports, and the same student may prefer different modes for different tasks.
2. Test the complete interaction, not just the feature list
Ask the learner to complete a real classroom task using their usual access method. Can they sign in, navigate controls, enter a question, understand the response, correct an error, and save or share the result? Test keyboard-only navigation, screen readers, magnification, speech input, switch access, captions, and audio playback where relevant. The W3C’s Web Content Accessibility Guidelines (WCAG) 2.2 provide a useful baseline for digital interface accessibility, including keyboard operation, but technical conformance alone does not guarantee that a learning activity is pedagogically accessible.
3. Reduce language and cognitive friction without removing the learning goal
Check whether learners can ask questions in the mode they can use comfortably and whether responses can be adjusted for length, vocabulary, structure, and modality. A useful tool might offer one instruction at a time, a worked example, audio playback, a visual sequence, or a choice between a short and detailed explanation. But simplification should not silently remove essential concepts or lower the intellectual demand of the task. Accessibility means removing unnecessary barriers while preserving meaningful opportunities to learn.
4. Keep educators in the loop
Use AI as a supported resource, not an automatic replacement for teacher judgement or established accommodations. Model how to ask a question, check an answer, request clarification, and recognise when the system has misunderstood. The four support domains identified by Tang and colleagues offer a practical planning prompt: What instructional, literacy, emotional-behavioural, and technological support might this activity require? The answer may change during the lesson, so staff should be able to adapt support in real time.
5. Protect learner agency and provide an alternative
Students should be able to decline a tool that does not work for them and use an appropriate alternative without being penalised. Explain what the AI is doing, allow learners to correct or reject its output, and avoid making a chatbot the sole route to an essential learning resource. Where possible, include learners with disabilities in tool selection and testing before procurement. This aligns with the Universal Design for Learning (UDL) principle of designing multiple ways to engage with information and express learning, rather than expecting every learner to use the same interface.
6. Review privacy, safety, and representation
Before using a system with students, document what data it collects, who can access it, how long it is retained, whether prompts or uploads may be used to improve the service, and how records can be deleted. Do not enter identifiable student information into unapproved services. Review whether the tool produces stereotyped or demeaning descriptions of disability, misreads non-standard language, or treats a communication difference as a lack of understanding. Keep a clear route for students and staff to report harmful outputs and pause use while serious issues are investigated.
7. Measure participation and learning separately
Record more than whether the learner opened the tool or completed an activity. Useful indicators might include whether the learner could begin the task independently, how often assistance was needed, whether they could explain or apply the target concept, whether they felt in control of the interaction, and whether the accommodation reduced an existing barrier. Use a baseline or comparison with the current approach where feasible. Collect feedback from the learner and educator, and avoid treating a small pilot as proof of broad effectiveness.
8. Check who is excluded by the rollout
Consider connectivity, device availability, licensing costs, language support, compatibility with existing assistive technology, and the time required for staff training. If a school adopts a tool that only works well on recent devices or for learners who can comfortably use text-based interfaces, it may widen the very gaps it aims to close. UNESCO’s emphasis on People, Products, Pedagogy, Policy, Place, and Provision is useful here: assess the whole environment, not just the product.
A six-week, low-risk pilot for schools
The following is a proposed implementation sequence, not a validated intervention protocol. It can help a school learn whether a particular AI tool is suitable before wider adoption.
- Week 1 — Define the goal: Select one learning barrier and one specific task. Agree on the learner’s preferred access methods and what success would look like.
- Week 2 — Co-test accessibility: Have the learner and staff test the actual workflow, including assistive technologies, alternative input methods, and failure cases.
- Weeks 3–4 — Run a limited pilot: Use the tool for a defined set of activities. Record support required, technical failures, learner feedback, and any safety or privacy concerns.
- Week 5 — Evaluate independently: Check whether the learner can demonstrate the intended knowledge or skill, with appropriate accommodations but without relying on the AI to supply the answer.
- Week 6 — Decide and document: Continue, modify, or stop the pilot based on predefined criteria. Record which learners benefited, what remained inaccessible, and what additional training or procurement conditions are needed.
Set stop conditions in advance. A privacy incident, repeated inaccessible interaction, harmful or discriminatory output, or a pattern of replacing rather than supporting the learner’s own participation should trigger review. If the pilot is small, describe its findings as local feasibility evidence. Do not present them as proof of effectiveness across disabilities, subjects, or school systems.
The strategic shift: from AI availability to inclusive capability
The emerging research points away from a narrow question—“Does this platform have AI accessibility features?”—toward a more demanding one: “Can this learner use this system to participate in this learning activity, with appropriate agency, support, and protection?” That shift makes accessibility a shared responsibility across procurement, pedagogy, professional development, governance, and product design.
For school leaders, the practical priority is not to buy the most sophisticated tool first. It is to identify the learner’s goal, co-test the real interaction, preserve alternatives, train staff, and measure meaningful participation and learning. AI may help remove barriers in some contexts; in others, it may introduce new ones. An inclusive strategy makes room for both possibilities and lets evidence—not marketing claims—guide the decision.
Sources and further reading
- Agius, M. (2026 release page; report text dated 2025). Report on the Use of AI and ICT to Support the Inclusion of Children with Autism, ADHD and Learning Disabilities. UNESCO Institute for Information Technologies in Education. The report draws on literature review, expert interviews, and case studies from 22 countries.
- Sakowicz, M., & Hamidi, F. (2026). Perspectives of special education teachers on AI-enabled technologies: accessibility, inclusion, and professional development needs. Universal Access in the Information Society. Published 28 July 2026.
- Tang, K.-S., Rappa, N. A., Nonis, K., & Ilyas, K. (2026). Supporting Students With Disabilities to Use Generative AI: A Classroom-Based Taxonomy of Educator Scaffolding Practices. Journal of Special Education Technology. First published online 12 May 2026.
- CAST. (2024). Universal Design for Learning Guidelines, Version 3.0. A research-informed framework for designing learning environments that reduce barriers and support learner agency.
- World Wide Web Consortium (W3C). (2024). Web Content Accessibility Guidelines (WCAG) 2.2. Technical guidance for making web content more accessible; it should complement, not replace, learner-centred pedagogical evaluation.
Evidence limitations: The cited studies include a global practice-oriented report and small qualitative research projects. They help identify design and implementation questions but do not establish that all AI tools improve learning for all students with disabilities. The six-week pilot above is a proposed local evaluation method, not a validated programme.