Ready-Willing-Able (RWA) Framework
What is the RWA Framework?
The Ready-Willing-Able Framework helps organizations assess their capacity for inclusive emergency communications.
Many organizations care about inclusion but struggle to implement it effectively.
The RWA Framework breaks this into three components:
- Willing - You want to do it
- Ready - You have the tools
- Able - You have the skills
Why This Matters
Most organizations are “Willing” (they have good intentions) but lack the “Ready” (pre-prepared materials) or “Able” (trained staff) components.
This framework helps you identify and close those gaps.
The Three Components
1. Willing: Motivation
Definition: Your organization values inclusion and has committed to it.
Common Gap: “We care about accessibility, but there’s no budget.”
What Success Looks Like:
- Leadership has signed an accessibility mandate
- Budget is allocated for accessible communications
- Inclusion is part of performance reviews
- Staff know that accessibility is a priority
Implementation Steps:
- Get leadership to sign a Universal Access commitment
- Add accessibility to department goals
- Create a dedicated budget line
- Include accessibility in job descriptions
2. Ready: Logistics
Definition: The materials, templates, and infrastructure exist before an emergency happens.
Common Gap: “We have no pre-translated alert templates.”
What Success Looks Like:
- Alert templates exist in multiple languages
- Easy Read versions are already created
- Alternative formats are pre-approved
- Distribution channels are tested
- Crisis Mode website is operational
Implementation Steps:
- Create alert templates now (don’t wait for a crisis)
- Pre-translate into community languages
- Save templates in your alert system
- Test sending through all channels
- Create Easy Read versions
- Set up automatic distribution
3. Able: Skills
Definition: Staff know how to create and distribute accessible communications.
Common Gap: “Our team doesn’t know how to write Plain Language.”
What Success Looks Like:
- Staff can write at Grade 6 reading level
- Team knows Easy Read principles
- Staff can create alt text for images
- Team can operate under stress
- Regular accessibility training happens
Implementation Steps:
- Conduct Plain Language training
- Practice Easy Read writing
- Train on alternative format creation
- Run emergency drills
- Review real examples
- Get feedback from people with disabilities
RWA Audit Scorecard
Use this scorecard to assess your organization.
Answer “Yes” or “No” to each question.
For every “No,” follow the linked resource to close the gap.
Willing: Leadership & Prioritization
- Has leadership signed an accessibility commitment?
- Yes
- No → Create a Universal Access mandate (see examples in CAN-ASC-6.4 Case Study)
- Is there a dedicated budget for accessible communications?
- Yes
- No → Review Resource Directory for funding justification guidance
- Are accessibility goals in staff performance reviews?
- Yes
- No → Incorporate accessibility metrics into performance evaluations
Willing Score: ___/3
Ready: Infrastructure & Templates
- Do pre-written alert templates exist?
- Yes
- No → Emergency Templates
- Are templates translated into community languages?
- Yes
- No → Multi-Platform Toolkit
- Is a low-bandwidth crisis mode available?
- Yes
- No → Crisis Mode Guide
- Are distribution channels tested regularly?
- Yes
- No → Digital Egress Checklist
- Do Easy Read versions exist for critical alerts?
- Yes
- No → Plain Language Toolkit
- Are alternative formats (audio, video, ASL) pre-approved?
- Yes
- No → Disability Spectrum Guide
Ready Score: ___/6
Able: Staff Competency
- Can staff write at Grade 6 reading level?
- Yes
- No → Plain Language Toolkit
- Do staff know Easy Read principles?
- Yes
- No → Plain Language Toolkit
- Have staff completed accessibility training in the last year?
- Yes
- No → Review Resource Directory for training resources
- Have emergency drills included accessible communications?
- Yes
- No → Incorporate accessibility testing into regular emergency drills
- Do staff know how to create alt text and captions?
- Yes
- No → Review WCAG guidelines in Resource Directory
- Has the team consulted with people with disabilities?
- Yes
- No → Contributing Guide explains how to engage the community
Able Score: ___/6
Interpreting Your Score
Total Score: ___/15
13-15 points: Excellent! You are ready for inclusive emergency communications.
10-12 points: Good progress. Focus on closing the remaining gaps.
7-9 points: Moderate readiness. Prioritize high-impact improvements.
4-6 points: Early stages. Start with leadership commitment and basic templates.
0-3 points: Significant gaps. Begin with the “Willing” component to establish organizational commitment.
Progressive Improvement: Start Where You Are
Do not wait for a perfect score.
You do not need 15/15 to save lives.
You need to be better today than you were yesterday.
Your First Week: Focus on Quick Wins
If you scored 0-3 points:
- Pick one template from Emergency Templates
- Send it to test your distribution channel
- That is progress
If you scored 4-6 points:
- Create 3 pre-written templates
- Add one new distribution channel
- Test both channels
- That is progress
If you scored 7-9 points:
- Complete one staff training session
- Create Easy Read versions of your top 3 alerts
- Run one emergency drill
- That is progress
If you scored 10+ points:
- Engage the disability community for feedback
- Document your process to share with others
- Mentor another organization
- That is progress
Track Your Improvement Over Time
Retake this assessment every 3 months.
Goal: Improve your score by 2-3 points each quarter.
Example Progress (assuming consistent 2-3 point improvement per quarter):
- Quarter 1: Score 4/15 (Built 3 templates, tested one channel)
- Quarter 2: Score 7/15 (Added Easy Read, trained staff on Plain Language)
- Quarter 3: Score 10/15 (Set up multi-channel alerts, ran first drill)
- Quarter 4: Score 13/15 (Consulted disability community, refined all templates)
This is realistic, achievable progress.
Remember: Progress Over Perfection
In a disaster, a 7/15 organization that acts fast saves more lives than a 15/15 organization that moves slowly.
Speed and progress matter more than perfect scores.
Your goal is improvement, not perfection.
Gap Analysis: What to Do Next
If You Scored Low on “Willing”
Priority: Get leadership buy-in.
Actions:
- Present the case for accessibility as a life-safety issue
- Show legal requirements (ADA, CAN-ASC-6.4)
- Share examples of emergency failures
- Request budget allocation
- Get written commitment
Resources:
If You Scored Low on “Ready”
Priority: Build infrastructure now, before an emergency.
Actions:
- Create alert templates using Easy Read
- Translate into top 3 community languages
- Set up Crisis Mode website mirror
- Test all distribution channels
- Pre-approve alternative formats
- Document the process
Resources:
If You Scored Low on “Able”
Priority: Train staff on accessibility best practices.
Actions:
- Schedule Plain Language workshop
- Practice writing Easy Read content
- Learn WCAG basics
- Conduct tabletop exercises
- Get feedback from disability community
- Make training annual requirement
Resources:
Real-World Example: Hurricane Response
Before RWA Framework
Situation: Hurricane approaching coastal city.
Willing: ✅ City cared about reaching everyone.
Ready: ❌ No pre-translated templates existed.
Able: ❌ Staff didn’t know Easy Read writing.
Result: Emergency messages sent in complex English only. Non-English speakers and people with cognitive disabilities missed critical evacuation orders.
After RWA Framework
Situation: Hurricane approaching coastal city.
Willing: ✅ City has Universal Access policy.
Ready: ✅ Pre-translated templates in English, Spanish, Vietnamese.
Able: ✅ Staff trained on Plain Language and Easy Read.
Result: Clear messages reached all residents. Multiple formats sent through SMS, social media, and local radio. Evacuation successful.
Using the RWA Framework
For Emergency Managers
-
Assess Your Current State: Complete the RWA Audit Scorecard.
-
Identify Priority Gaps: Focus on areas with lowest scores.
-
Create Action Plan: Use linked resources to address gaps.
-
Set Timeline: Assign deadlines for each improvement.
-
Regular Review: Reassess quarterly.
For Policy Makers
-
Require RWA Assessment: Make it part of emergency planning.
-
Fund Infrastructure: Allocate budget for “Ready” components.
-
Mandate Training: Ensure “Able” through required accessibility training.
-
Track Progress: Monitor RWA scores across departments.
For Standards Bodies
-
Reference RWA: Use as self-assessment tool.
-
Collect Data: Track RWA scores across jurisdictions.
-
Identify Patterns: See where organizations struggle most.
-
Refine Standards: Use gaps to inform policy updates.
Continuous Improvement
The RWA Framework is not a one-time assessment.
Reassess Regularly:
- After every emergency (lessons learned)
- When staff change (maintain “Able”)
- When technology changes (update “Ready”)
- Annually (minimum)
Update Materials:
- Templates need refreshing
- Languages may change
- Technology evolves
- Standards are updated
Stay Connected:
- Join emergency management networks
- Participate in accessibility forums
- Share what works
- Learn from others
Additional Resources
Self-Assessment Tools
Implementation Guides
Standards & Research
Questions?
Found a gap in the RWA Framework? Open an issue.
Want to share your RWA journey? Contribute your story.
Need help implementing? Review the Resource Directory for expert guidance.
The RWA Framework helps you move from good intentions to effective action. Start today.