Dyslexia classification can widen support or deepen exclusion
Updated Jul 04, 2026
student voiceUniversities can promise inclusion and still make disability support feel like a test of endurance. At Student Voice AI, we often see the same pattern in student voice: small barriers around disclosure, paperwork, teaching practice, and staff understanding accumulate until students decide support is not worth the cost of asking. That is why Charlotte Hamilton Clark and Martin Oliver's Teaching in Higher Education paper, "Explanation, engagement, exclusion: students’ negotiations with dyslexia classification in UK universities", matters. It shows that dyslexia is not experienced as one stable category inside a university. It is continually interpreted through tests, rules, spaces, and relationships, each of which can make support more usable or more alienating.
Context and research question
The paper starts from a practical tension that many UK universities will recognise. Institutions say they want inclusive support, but dyslexia has to pass through several institutional filters before that support becomes real: diagnostic evidence, disclosure decisions, legal categories, funding rules, and day-to-day teaching practice. Each filter defines the student's needs slightly differently, which means the route to support can become a second challenge in its own right.
Clark and Oliver examine that tension through students' experiences of dyslexia in UK universities, using Annemarie Mol's idea of multiplicities to link lived experience with the politics of classification. The aim is not to settle an abstract debate about whether dyslexia is "real". It is to ask how different institutional versions of dyslexia are enacted, and what those versions do to students' self-understanding, support use, and ability to progress.
Key findings
The central finding is that dyslexia is enacted in multiple, sometimes conflicting ways inside the same institution. Medical explanations, legal disability definitions, standardised testing, funding requirements, and staff beliefs can all shape what dyslexia is taken to mean. For universities, the practical point is clear: inclusion does not fail only when a support service is absent. It can also fail when the systems around that service pull students in different directions.
Classification itself can both open doors and create new forms of strain. A diagnosis may unlock adjustments, validation, or a clearer explanation for longstanding difficulty. But the same process can also demand burdensome testing, push students towards narrow categories, or leave them negotiating whether disclosure will bring support or stigma. That sits close to wider work on what belonging can mean for students from marginalised groups: access depends not only on formal entitlement, but on whether students feel recognised without being reduced to a label.
Support is shaped by ordinary institutional conditions, not only by disability policy. The abstract highlights diagnostic tests, physical spaces, and staff attitudes as mechanisms that enact dyslexia differently. That matters because a university can publish an inclusive policy and still make seminars, learning materials, or support routes feel inaccessible in practice. Disability inclusion therefore sits with teaching teams, estates, timetabling, and communications as much as with specialist services.
The paper's sharpest warning is about what follows from those arrangements:
"These create consequences for students, affecting their self-concept, their engagement or withdrawal from support services, and their ability to progress with their courses."
The consequence is not only frustration. It can alter self-concept, support use, and progression. For UK teams, that matters because a student stepping back from support is not necessarily showing low motivation or low need. They may be responding rationally to a system that feels exposing, inconsistent, or exhausting.
Practical implications
First, UK universities should audit the full dyslexia journey rather than treating disability support as a single-office function. Review evidence requirements, disclosure routes, reasonable adjustments, staff guidance, and learning-platform accessibility as one connected experience. If students have to repeat the same explanation at every stage, the process is already doing part of the excluding. The benefit is a support route students can use without having to keep proving they deserve help.
Second, institutions should ask more precise open-text questions about support experience. A broad item on satisfaction with disability support will miss the mechanism. Ask what made disclosure easier or harder, what happened after students shared information, and which parts of teaching or administration made support feel usable. That matters because exclusion often accumulates over time, much like the later-emerging gaps seen in research on belonging changing across the first year. The benefit is earlier evidence on where friction is building before it turns into disengagement or withdrawal.
Third, universities should separate disability-related themes before acting on feedback. Administrative friction, assistive technology, staff understanding, teaching design, and physical access are different problems with different owners. This is where Student Voice Analytics fits naturally: it helps teams group free-text comments into those operational categories at scale, so student experience and disability teams can prioritise fixes with clearer ownership. The benefit is faster action and less risk of collapsing every problem into a vague "support issue".
Finally, teams should treat dyslexia-related comment analysis as a governance issue as well as an insights task. Feedback about disclosure, diagnosis, adjustments, and support use can be highly sensitive, especially in smaller cohorts. A documented process such as our student comment analysis governance checklist helps universities decide what to collect, who should see it, and how to route it responsibly. The benefit is better evidence without asking students to trade privacy for participation.
FAQ
Q: How should a university redesign dyslexia support after reading this paper?
A: Start by mapping the student journey end to end, not service by service. Check where students first recognise a difficulty, how they are told to seek evidence, what happens after disclosure, how adjustments are communicated to staff, and where follow-through breaks down. Then add one or two open-text questions to an existing survey or review cycle so students can explain which parts of that journey feel supportive and which parts feel risky.
Q: What should teams keep in mind before generalising from this study?
A: This is an interpretive paper focused on UK universities and the politics of classification, so it is strongest on mechanisms rather than prevalence. It shows how inclusion and exclusion can be produced through ordinary institutional arrangements, but it does not claim that every dyslexic student or every university will experience those arrangements in the same way. The right use is to sharpen what you ask, listen for, and test in your own context.
Q: What does this change about student voice practice more broadly?
A: It broadens what counts as relevant evidence. Comments about disclosure, support use, and accessibility are not just service feedback. They are evidence about how inclusion is being enacted in practice. That makes free-text student voice especially valuable, because students can describe the chain of decisions, interactions, and small barriers that a headline satisfaction score will never show on its own.
References
[Paper Source]: Charlotte Hamilton Clark, Martin Oliver "Explanation, engagement, exclusion: students’ negotiations with dyslexia classification in UK universities" DOI: 10.1080/13562517.2026.2695806
Request a walkthrough
Book a free Student Voice Analytics demo
See all-comment coverage, sector benchmarks, and reporting designed for OfS quality and NSS requirements.
- All-comment coverage with HE-tuned taxonomy and sentiment.
- Versioned outputs with TEF-ready reporting.
- Benchmarks and BI-ready exports for boards and Senate.
UK-hosted · No public LLM APIs · Same-day turnaround