10 minutes
Why disability data helps, and where it harms See what disability data can reveal about barriers, why the same data creates privacy and trust risks, and how to decide whether to collect it at all.
What you’ll be able to do Explain how disability data supports equity work and identify the privacy, trust and misuse risks that must be managed before any collection begins. Compare the responses to this question and explain your choice: What is the most useful response from the accessibility coordinator? Document a next step for Why disability data helps, and where it harms: Find one place where your unit already asks about disability or access needs. Write down why it asks, who sees the answer and what changed because of it. If you cannot answer all three, raise it with the owner. Two truths at once Disability data can show that accommodation requests take six weeks in one division and six days in another, that public notices from one program fail accessibility checks far more often than another’s, or that disabled participants leave a service earlier than others. Without this information, barriers stay invisible and equity work runs on anecdote. The Centers for Disease Control and Prevention estimates that about one in four adults in the United States has a disability, so when a program’s data shows two percent, the number is describing who felt safe enough to say so.
The same data carries risk. Disability status is sensitive personal information. In a small team it identifies people even when names are removed. It can be misread as a cause of low performance, used to steer people away from opportunities, or shared beyond the purpose it was collected for. Every one of those harms lands on people who already carry more than their share of scrutiny.
Practitioners hold both truths. The skill is not choosing between collecting and not collecting; it is designing collection, analysis and reporting so the data describes systems and protects people.
Five questions before you collect anything What barrier or outcome are we trying to see, and could we see it without asking about disability status at all?
What is the smallest set of information that would answer the question?
Who will see the raw answers, where will they live, and how long will they be kept? In Minnesota government, the agency’s data practices office answers how the data is classified.
How will results be broken down, and what is the smallest group we will ever report on?
How and when will people who answered learn what the results were and what changed?
A number that helps you fix a form, a meeting or a process is equity data. A number that helps you form an opinion about a named person is surveillance. The difference is decided by design, not by intention.
Name the barrier before the question What you can change You control whether a request for disability data starts with a barrier or with curiosity.
What to watch for Do not approve a disability question because someone says it would be “good to know.” Ask what they will change if the answer is yes, and what they will change if it is no.
Your next step The next time someone proposes collecting disability data, write the purpose statement with them before anything else is designed.
Words the data work depends on Data minimization
Collect the least information that answers the question. If “do you need materials in a different format?” answers it, do not ask “what is your disability?”
Purpose limitation
Use the information only for the reason it was collected. Accommodation records opened to arrange an interpreter are not a source for a productivity discussion.
Aggregate
Combine individual answers into counts, percentages or averages so no single person’s response can be read from the result.
Disclosure
A person choosing to share their disability. It is theirs to give, can be partial, and can be withdrawn. Data collection must never make it feel required.
Sharing back
Telling the people who answered what the results showed and what changed because of them. Without it, the next response rate falls.
Carry this forward Data about disability is useful when it points at a barrier the organization can remove; it is harmful when it points at a person the organization can judge.
The Centers for Disease Control and Prevention estimates that about one in four adults in the United States has a disability, so low numbers in your data usually describe reluctance to disclose, not absence.
Purpose, minimum collection, secure handling and a plan to share results back are decided before the first question is asked.
A written purpose statement for one data collection, with the barrier it is meant to find and the risk it must manage.
Find one place where your unit already asks about disability or access needs. Write down why it asks, who sees the answer and what changed because of it. If you cannot answer all three, raise it with the owner.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Course overview Next lesson Carry this into practice Use disability data to find and remove barriers while protecting the people the data describes.
Return to the experience: What did you notice or try, whose perspective informed it, and what would you keep or adjust?
Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
