Framework Matrix

Three Frameworks, One Goal

Emergency communication must be:

  1. Accessible (WCAG 2.2)
  2. Sustainable (WSG 1.0)
  3. Understandable (Plain Language)

This matrix shows how they work together.

Translation Layer: Standards to Practice

This table shows how technical standards translate to practical emergency needs:

Pillar WCAG 2.2 Role WSG 1.0 Role Plain Language Role
Alerts Ensures screen readers can announce “Flash Alerts” immediately. Minimizes payload so alerts don’t fail on congested networks. Replaces “Evacuate the vicinity” with “Leave the area now.”
Maps Requires text-alternatives for GIS data and high-contrast color. Uses SVG instead of heavy JPGs to save battery and data. Focuses on clear landmarks rather than complex coordinates.
Manuals Mandates tagged PDFs or (better) accessible HTML. Encourages “Offline-First” via PWAs (Progressive Web Apps). Uses “How-To” active voice for medical/prep instructions.

The Emergency Alert Matrix

Emergency Need WCAG 2.2 WSG 1.0 Plain Language
Text Readability 1.4.3 Contrast (AA): 4.5:1 minimum 2.5 Readable Text: Sufficient contrast Use short words. Use short sentences.
Images 1.1.1 Non-text Content: Alt text required 3.3 Optimize Images: Compress, use WebP Describe what matters. Skip decoration.
Page Load 2.4.5 Multiple Ways: Fast navigation 1.1 Page Weight: Under 1MB Critical info first. Details can wait.
Mobile Access 1.4.10 Reflow: Work at 320px width 2.3 Mobile-First: Optimize for mobile Short paragraphs. Bullets. Numbers.
Offline Access N/A (not covered) 2.7 Offline-First: Cache critical content Include phone numbers. Include addresses.
Language 3.1.5 Reading Level: AAA recommends lower secondary 2.5 Readable Text: Simple language Grade 6 reading level. Active voice.
Navigation 2.4.1 Bypass Blocks: Skip links 1.2 Efficient Code: Minimize HTML Main action at top. No menus needed.
Color 1.4.1 Use of Color: Never color alone 2.2 Dark Mode: Support user preference Say “red zone” not “the red area.”
Forms 3.3.2 Labels: Clear form labels 1.3 Reduce Scripts: Minimize JavaScript One question per field. Example shown.
Updates 4.1.3 Status Messages: Announce changes 1.5 Update Frequency: Cache wisely “New: [Information]” at the top.

Deep Dive: Alert Text

WCAG 2.2 Requirements

1.4.3 Contrast (Minimum) - Level AA

3.1.5 Reading Level - Level AAA

2.4.6 Headings and Labels - Level AA

WSG 1.0 Requirements

2.5 Provide Accessible, Usable, Minimal Content

1.1 Undertake Systemic Impacts Assessment

Plain Language Requirements

Short sentences:

Common words:

Active voice:

Example: Evacuation Alert

❌ FAILS All Three Frameworks

EMERGENCY NOTIFICATION

Pursuant to municipal bylaw 2024-15, residents domiciled within 
the geographical boundaries designated as evacuation zones A 
through D are hereby mandated to vacate their premises and 
relocate to approved emergency shelter facilities or alternative 
accommodations outside the demarcated impact perimeter. 
Vehicular egress should be facilitated via arterial roadways 
as delineated in the municipal emergency response protocol.

For additional information, please consult our website or 
contact the emergency operations center.

WCAG Failures:

WSG Failures:

Plain Language Failures:

✅ PASSES All Three Frameworks

EVACUATION ORDER

You must leave now.

Who: Everyone in zones A, B, C, D

When: Leave in the next 2 hours

Where to go: Main Street School (100 Main St)

How: Drive north on Highway 1
     Or take the bus from City Hall (leaves every 30 minutes)

Need help? Call 555-1234

[Map showing evacuation zones]
[Map showing route to shelter]

WCAG Compliance:

WSG Compliance:

Plain Language Compliance:

Cross-Framework Techniques

Technique 1: Chunking

Meets:

Implementation:

## What to Do
1. Turn off gas
2. Lock doors
3. Take your medicine

## Where to Go
Main Street School
100 Main Street

## How to Get There
Take Highway 1 north

Technique 2: Progressive Disclosure

Meets:

Implementation:

SHELTER OPEN

Address: 100 Main Street
Phone: 555-1234

[Details link] (optional: hours, amenities, capacity)

Technique 3: Multi-Modal Content

Meets:

Implementation:

Priority Matrix

When time is limited, prioritize:

Priority Must Have Should Have Nice to Have
WCAG Level A compliance Level AA compliance Level AAA compliance
WSG Under 1MB page weight Under 500KB Under 100KB
Plain Language Grade 6 reading level Grade 4 reading level Easy Read version

Testing Against All Three

Step 1: WCAG Testing

Step 2: WSG Testing

Step 3: Plain Language Testing

Real-World Application

Scenario: Wildfire Evacuation

Context:

Framework Integration:

WCAG:

WSG:

Plain Language:

Common Mistakes

Mistake 1: Meeting WCAG But Not WSG

Heavy page with perfect accessibility that won’t load on slow internet.

Solution: Optimize first, accessorize second.

Mistake 2: Plain Language But Not Accessible

Simple text in an image without alt text.

Solution: Use HTML text, add image support.

Mistake 3: Sustainable But Not Clear

Tiny page that uses technical jargon.

Solution: Size efficiency doesn’t mean information efficiency.

The Bottom Line

WCAG ensures technical accessibility.

WSG ensures practical accessibility.

Plain Language ensures cognitive accessibility.

All three are required.

None are optional.

Emergency communication must be accessible, sustainable, and understandable.

This matrix is your guide.

**Pro Tip:** Print this matrix. Reference it during emergency alert creation. Check all three columns for every alert.

Additional Resources

For a comprehensive directory of global standards, academic research, and practical toolkits, see our Global Standards & Cognitive Accessibility Resources page.

WCAG 2.2:

WSG 1.0:

Plain Language: