If your organisation posts about International Day of People with Disability — then ships an inaccessible PDF the next day — that disconnect isn’t a slip-up. It’s disabilitywashing.
What do I mean by ‘disabilitywashing’?
Disabilitywashing is the gap between what an organisation says about disability inclusion and what it does. It shows up when disability is used as a brand asset — to look progressive, compassionate, or community-minded — without the structure, budget, or accountability to back it up.
It’s not always malicious. Sometimes it’s well-meaning teams trying to “do something” fast. But good intentions don’t change the impact when disabled staff and customers still hit the same barriers.
What disabilitywashing looks like in practice
Campaigns without access. A glossy post about inclusion… linking to an image with no alt text, video with no captions, or a registration form that doesn’t work with screen readers.
Moments without momentum. A one-day celebration, panel, or morning tea — and nothing changes in policy, procurement, or performance expectations afterwards.
Hero stories over hard systems. Spotlighting one person’s “overcoming” narrative while the workplace remains inaccessible, under-resourced, and risk-averse.
Commitments without cost centres. “We value inclusion,” yet there’s no budget line for reasonable adjustments, consultation, or accessible comms.
Data without duty of care. Asking people to disclose disability for a dashboard, with no clear purpose, safeguards, or follow-through to reduce risk and improve experience.
Committees without clarity. Standing up an “advisory group” — unpaid, no Terms of Reference, no decision-making power, and no mechanism to report back on what changed.
Procurement that forgets people. Renewing platforms, venues, or tools that are known to be inaccessible because “the contract’s already in flight”.
Why it’s a problem (beyond reputational risk)
It erodes trust. When people see big claims and small delivery, they stop engaging — surveys, focus groups, consultations all suffer.
It wastes effort. Staff pour time into “raising awareness” while the needle-moving work (rules, roles, resources) stalls.
It causes harm. Asking for lived experience without safety, compensation, or action re-creates the extractive dynamics inclusion is meant to fix.
It hides the real work. Disabilitywashing makes it look like inclusion is handled by Comms, when it’s actually a leadership, governance, and operations job.
A quick self-check: are we at risk of disabilitywashing?
Use this five-minute audit before your next announcement or “inclusion moment.”
Purpose: Can we explain why this matters now and what will be different three months after it?
People: Who has been involved in co-design? Were disabled people paid for their time?
Access: Are comms, events, venues, and tools accessible by default (not by exception)?
Power: Where does decision-making sit? Who can say “no” to a shiny idea that undermines inclusion?
Proof: What budget, policy, and procurement changes back this up? How will we measure outcomes and experience?
Protection: If we collect disability data, have we been explicit about purpose, safeguards, storage, and options not to disclose?
If you hesitate on more than one, pause the post — fix the system — then communicate.
What good looks like (and feels like)
Co-design from the start. Not “we built it, tell us what you think,” but “help shape the brief, constraints, and criteria.” Pay people for lived expertise.
Access in the backbone. Accessible formats, captioning, AUSLAN, plain-English summaries, tactile maps, lighting and acoustics considered, quiet rooms in event plans, and digital tools that meet accessibility standards.
Budget + governance. A visible cost centre for adjustments and access; a senior sponsor who owns decisions and outcomes; a public roadmap with dates.
Accountable procurement. Accessibility is a must-have, not “nice to have next phase.” Contracts include remediation clauses and penalties for non-compliance.
Real metrics. Track more than attendance and impressions. Look at time-to-adjustment, proportion of roles designed flexibly, retention, promotion, and qualitative feedback on safety and belonging.
Continuity. A cadence of actions across the year (policy, tools, training, recruitment, built environment), not one splashy week in December.
Mini-scenarios (you can borrow these internally)
The Launch: Your team wants a feel-good video for IDPwD. You redirect budget towards captioning, AUSLAN, and a small paid co-design sprint to improve your onboarding adjustments process — then share that change with a short, accessible explainer.
The Dashboard: Leadership wants disability disclosure metrics. You propose a two-step approach: improve privacy and adjustments workflows first, pilot a voluntary, purpose-led question set with clear comms and opt-outs second.
The Event: Facilities offers a stunning heritage venue for your forum. You decline because access can’t be guaranteed — and you publish your venue checklist so others learn from it.
The Disabilitywashing Red Flags (save this list)
“We’ll add accessibility later.”
“We couldn’t find anyone with lived experience in time.”
“Let’s just get the post out — we can revisit the detail next year.”
“Our vendor says they meet standards” (no evidence, no testing).
“We don’t have a budget line for that.”
“The committee can advise, but the decision is already made.”
How to pivot from disabilitywashing to meaningful change
Map the barriers. Where are people currently excluded — hiring, onboarding, performance, meetings, spaces, systems, comms? Name the pain points and quantify the risk.
Prioritise two moves per quarter. E.g., Q1: reasonable adjustments policy + quick-turn funding process; Q2: recruitment pack refresh + accessible job ad templates; Q3: procurement standard + venue checklist; Q4: manager capability uplift + reporting.
Resource it. Allocate a budget for adjustments, access services, and paid co-design. Protect time in key roles to do the work.
Set public milestones. Share what’s changing and when — then report honestly on progress and what you’ve learned.
Close the loop. If you asked for input, publish outcomes. Be explicit about what you could and couldn’t do, and why.
Embed, don’t add. Bake inclusion into existing governance (risk, finance, procurement, people & culture), not just campaigns.
Over to you
Where does your organisation do great storytelling but struggle with systems?
If you could redirect one “awareness” budget to a structural fix, what would you fund first?
What would make you feel safe to contribute — and confident it won’t become unpaid emotional labour?
Hit reply or leave a comment and tell me what you’re seeing — the good, the bad, and the quietly powerful.
