Enterprise · A practical reflection guide
How to evaluate your accessibility culture
Examine what your organization repeatedly prioritizes, supports, and does—not just what its policies say.
Working guidance, not a validated assessment. These six review areas are practical organizing prompts, not a claim that they are the study’s validated constructs or scales. Do not use the descriptions to certify conformance, rank organizations, or produce an ACLT score. Culture review complements technical accessibility testing; it does not establish WCAG or legal compliance.
Run an evidence-informed conversation
- Define the scope. Choose a customer or employee journey, such as purchasing a product, opening an account, applying for a job, or using an internal system. Name the teams, systems, and time period covered. Start with a manageable scope rather than claiming to evaluate the whole organization.
- Bring different perspectives. Include a decision maker, people doing the work, accessibility expertise, and people affected by barriers. Offer accessible formats, more than one way to contribute, and appropriate support for participation.
- Gather examples before judging. Combine conversations, work artifacts, and observed practice. A policy shows an intention; examples show whether it is used. As a practical starting point, seek two recent examples where feasible, without treating that as a validation threshold.
- Discuss the six areas. Record what supports each judgment and any disagreement. Separate missing evidence from evidence that a practice is absent. Look for counterexamples and exceptions.
- Choose one or two changes. Identify who can act, what support they need, what evidence would show progress, and when you will review it together.
Privacy: Use approved organizational processes. Record de-identified patterns and document references rather than student records, patient information, personnel details, or identifiable accounts of disability.
Describe practice without inventing a score
Select the description best supported by evidence within the scope you reviewed. Different areas may have different descriptions. Do not average them. A small pilot cannot establish an organization-wide pattern.
| Description | What it means |
|---|---|
| Unclear | Evidence is missing, conflicting, or too limited to judge. Record what you need to learn. |
| Person-dependent | The practice happens mainly through individual effort, exceptions, or reminders. |
| Defined & supported | Ownership, expectations, resources, and a repeatable process are documented and used in the reviewed scope. |
| Embedded & learning | Multiple examples over time show the practice continuing across people and teams, with feedback shaping improvements. |
Worksheet: Notes entered below stay on this page only and are not saved or submitted. Print or save as PDF before leaving. Avoid confidential information.
Review area 1
Leadership & purpose
Ask together
Can executives connect accessibility to the organization’s purpose and demonstrate resource decisions that support it?
Look for evidence
Business plans, executive meeting records, staffing and budget decisions, and interviews across functions.
A sign of culture in practice
A leader funds a reusable accessible component rather than requiring each team to solve the same barrier independently.
Review area 2
Governance & decision authority
Ask together
Who owns accessibility decisions across product, procurement, HR, and support—and who has authority when priorities conflict?
Look for evidence
Product approval criteria, procurement requirements, decision rights, vendor agreements, and escalation records.
A sign of culture in practice
A product owner can bring an unresolved barrier into a release decision with a named decision maker and documented follow-up.
Review area 3
Everyday practice & accountability
Ask together
Is accessibility part of discovery, design, development, content, purchasing, and support as routine work?
Look for evidence
Requirements, design-system guidance, completed review records, backlog patterns, and samples of shipped experiences.
A sign of culture in practice
A feature team includes accessibility expectations in its acceptance criteria before development begins.
Review area 4
Learning & capability
Ask together
Do people know what accessibility requires in their own role and have usable support when they are unsure?
Look for evidence
Role-based onboarding, practical exercises, office hours, team interviews, and examples of learning applied to work.
A sign of culture in practice
Procurement staff can interpret the purpose and limitations of vendor accessibility documentation and know when to seek specialist help.
Review area 5
Participation & belonging
Ask together
Are employees and customers with disabilities able to influence decisions with meaningful follow-through?
Look for evidence
Research recruitment practices, employee feedback routes, support themes, and decision records showing how feedback was used.
A sign of culture in practice
A recurring employee barrier changes an internal platform requirement rather than remaining an individual workaround.
Review area 6
Feedback & continuous improvement
Ask together
Do teams track recurring causes and check whether process changes improve outcomes over time?
Look for evidence
Retrospectives, customer support trends, repeated defect analysis, ownership records, and follow-up reviews.
A sign of culture in practice
A recurring checkout barrier leads to design-system and release-process changes, followed by a review of the customer experience.
Turn the review into a practical next step
Choose a recurring barrier or organizational condition that matters to people affected and that your team can influence. Consider impact, repetition, decision authority, and the support required. Avoid choosing only the easiest item or only the area with the least documentation.
- Name the finding: “Within this journey, we observed… supported by… with these uncertainties…”
- Name the change: Specify one decision or recurring practice to improve.
- Assign authority and support: Agree an owner, decision maker, time, resources, and a route for escalation.
- Define evidence of progress: Identify what would show changed practice and an improved experience, alongside any relevant technical checks.
- Set a review date: Revisit in 30–90 days, using the same scope where possible. Ask what changed, what did not, and what you learned.
Keep a short record of the scope, participants’ roles, evidence dates, findings, differing views, priorities, owners, and review date. Share an accessible summary with participants and invite corrections.
Discuss your findings
These guides are starting points for organizational reflection and improvement. For questions about applying the approach in enterprise, contact Dr. Deb.