Accessibility Statement
⚡ Quick Summary
- ✅ WCAG 2.2 Level AA compliant (82% AAA)
- ✅ Works with all screen readers
- ✅ Full keyboard navigation
- ✅ Dark mode & high contrast options
- ✅ Dyslexia-friendly fonts available
- ✅ No time limits on any actions
Need help? Contact our accessibility team
---
## 📚 Table of Contents
**Jump to any section below:**
---
---
## Our Commitment
We believe accessibility isn't just compliance—it's a core value. Our platform is designed to serve **persons with disabilities, injured workers, and everyone** navigating complex systems. We prioritize:
---
## Accessibility Goals
We strive to ensure 3mpwrApp is accessible to all users, including those with:
---
## 3mpwrApp Features
For detailed documentation of all accessibility features, please see our comprehensive **[User Guide](/user-guide/)** which covers:
- **Cognitive Accessibility** - Simplified modes, auto-save, progress tracking
- **Dyslexia Support** - Special fonts, colored overlays, spacing controls
- **Motor Enhancements** - Keyboard shortcuts, large targets, voice commands (planned)
- **Screen Reader Optimization** - ARIA labels, semantic structure, skip links
- **Visual Customization** - High contrast, dark mode, text sizing
- **Indigenous Cultural Considerations** - Culturally appropriate accessibility features
Additional resources:
- [Accessibility Settings](/accessibility-settings/) - Customize your experience
- [Accessibility Walkthrough](/accessibility-walkthrough/) - Guided feature tour
- [Roadmap](/roadmap) - Planned accessibility improvements
---
## Compliance Status
### WCAG 2.2 Level AAA Conformance
We meet **all** WCAG 2.2 Level A, Level AA, and Level AAA success criteria, achieving **maximum accessibility** standards:
**Full AA Compliance Checklist:**
### What we've tested:
View Latest Accessibility Report →
### W3C Standards Compliance
In addition to WCAG 2.2 Level AAA conformance, 3mpwrApp website adheres to **W3C HTML5 and CSS3 standards**:
**Standards Verified:** November 5, 2025
**Validation Tools:** W3C Markup Validator, W3C CSS Validator, Manual Review
View Full W3C Compliance Details →
---
## Known Limitations
**We practice radical transparency about accessibility gaps:**
---
## Feedback and Support
**We want to hear from you!** If you:
- Encounter an accessibility barrier
- Have suggestions for improvement
- Need assistance accessing content
- Want to report an issue
**Contact us:**
- **Email:** [[email protected]](mailto:[email protected])
- **Subject line:** "Accessibility Feedback"
- **Use our [Contact Form](/contact/)**
- **Phone:** Available upon request for urgent accessibility issues
**Response Time:**
- **Urgent accessibility barriers:** Within 24 hours
- **General feedback:** Within 2 business days
- **Feature requests:** Reviewed weekly
**Alternative Contact Methods:**
- **Social Media:** [Facebook](https://www.facebook.com/3mpowrapp), [X/Twitter](https://x.com/3mpowrApp0816), [Instagram](https://www.instagram.com/3mpowrapp/)
- **Community Forums:** [3mpwrApp Community](/community) - accessible discussion
- **Anonymous Feedback:** Use [Anonymous Feedback Form](/feedback) if you prefer not to identify yourself
**Accessibility Coordinator:**
- Name: Accessibility Team
- Email: [[email protected]](mailto:[email protected])
- Responsible for: Coordinating accessibility improvements, responding to barriers, conducting audits
We aim to provide reasonable accommodations and will work with you to ensure you can access all content and features.
---
## Standards and Guidelines
We follow these recognized standards:
- [WCAG 2.2 (Web Content Accessibility Guidelines)](https://www.w3.org/WAI/WCAG22/quickref/)
- [ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/)
- [Section 508 Standards](https://www.section508.gov/)
- [Accessible Canada Act (ACA)](https://laws-lois.justice.gc.ca/eng/acts/A-0.6/)
- [Accessibility for Ontarians with Disabilities Act (AODA)](https://www.ontario.ca/laws/statute/05a11)
---
## Continuous Improvement
### Recent Improvements:
- ✅ Implemented cognitive accessibility modes
- ✅ Added dyslexia-friendly fonts and overlays
- ✅ Enhanced keyboard navigation throughout site
- ✅ Improved screen reader support with ARIA labels
- ✅ Added high contrast and dark mode themes
### Upcoming Improvements:
See our **[Roadmap](/roadmap)** for planned accessibility features including:
- 🔜 Motor disability enhancements (dwell-click, voice commands)
- 🔜 Enhanced screen reader optimization
- 🔜 Accessibility hardware support (eye-tracking, switches)
- 🔜 Indigenous cultural protections and protocols
---
## Legal Compliance
### Canadian Compliance
We are committed to meeting the requirements of:
- **Accessible Canada Act (ACA)** - Federal accessibility legislation
- **Accessibility for Ontarians with Disabilities Act (AODA)** - Ontario provincial law
- **Provincial accessibility legislation** across Canada
### International Standards
We also work toward compliance with:
- **WCAG 2.2 Level AA** (W3C international standard)
- **Section 508** (United States federal standard)
- **European Accessibility Act** requirements
---
## Related Pages
### Documentation
Quick Summary
- ✅ WCAG 2.2 Level AA compliant
- ✅ Screen reader optimized (JAWS, NVDA, VoiceOver tested)
- ✅ Full keyboard navigation support
- ✅ High contrast & dark mode options
- ✅ Dyslexia-friendly fonts & overlays
- ✅ No time limits on any actions
Need help? Customize your accessibility settings or contact our accessibility team.
Universal Access
Everyone should be able to use 3mpwrApp, regardless of ability
Continuous Improvement
We regularly audit and enhance our accessibility features
User-Centered Design
We listen to feedback from our community and implement changes
Transparency
We document our progress and acknowledge areas for improvement
Visual Impairments
Screen reader support, high contrast modes, keyboard navigation
Cognitive Disabilities
Simplified modes, clear language, predictable navigation
Motor Disabilities
Keyboard-only navigation, large click targets, no time limits
Hearing Impairments
Captions on videos, visual alternatives for audio content
WCAG 2.2 Level AAA
Maximum Accessibility
W3C HTML5
Valid & Compliant
W3C CSS3
Valid & Compliant
Last Audit: November 5, 2025
Testing Method: Automated (axe-core, pa11y, Lighthouse) + Manual Testing
Pages Tested: 15+ pages (English & French)
Violations Found: 0
📄 View Full Audit Report
Level AAA Achievements (Gold Standard):
Color Contrast: 10.2:1 ratios (AAA requires 7:1, far exceeds standard)
Enhanced Contrast: High contrast modes exceed all AAA requirements
Focus Indicators: Enhanced visual focus (2px minimum)
Target Size: 44x44px minimum (exceeds AA 24x24px requirement)
Perceivable (25 criteria) - 100% compliant
**Text Alternatives:** - ✅ 1.1.1 Non-text Content (A) - All images have descriptive alt text **Time-based Media:** - ✅ 1.2.1 Audio-only and Video-only (A) - Transcripts provided - ✅ 1.2.2 Captions (A) - All videos captioned - ✅ 1.2.3 Audio Description or Media Alternative (A) - Transcripts available - ✅ 1.2.4 Captions (Live) (AA) - Live captions when applicable - ✅ 1.2.5 Audio Description (AA) - Provided for video content **Adaptable:** - ✅ 1.3.1 Info and Relationships (A) - Semantic HTML structure - ✅ 1.3.2 Meaningful Sequence (A) - Logical reading order - ✅ 1.3.3 Sensory Characteristics (A) - Instructions not shape/color dependent - ✅ 1.3.4 Orientation (AA) - Works in portrait and landscape - ✅ 1.3.5 Identify Input Purpose (AA) - Autocomplete attributes used **Distinguishable:** - ✅ 1.4.1 Use of Color (A) - Color not sole method of conveying info - ✅ 1.4.2 Audio Control (A) - No auto-playing audio - ✅ 1.4.3 Contrast (Minimum) (AA) - 4.5:1+ text, 3:1+ UI (we exceed: 7:1+) - ✅ 1.4.4 Resize Text (AA) - Text resizable to 200% - ✅ 1.4.5 Images of Text (AA) - Minimal use, real text preferred - ✅ 1.4.10 Reflow (AA) - No horizontal scrolling at 320px width - ✅ 1.4.11 Non-text Contrast (AA) - UI components 3:1+ (we use 4.5:1+) - ✅ 1.4.12 Text Spacing (AA) - Supports custom spacing - ✅ 1.4.13 Content on Hover or Focus (AA) - Dismissible, hoverable, persistentOperable (30 criteria) - 100% compliant
**Keyboard Accessible:** - ✅ 2.1.1 Keyboard (A) - All functionality keyboard accessible - ✅ 2.1.2 No Keyboard Trap (A) - No focus traps - ✅ 2.1.4 Character Key Shortcuts (A) - Can be remapped/disabled **Enough Time:** - ✅ 2.2.1 Timing Adjustable (A) - No time limits on actions - ✅ 2.2.2 Pause, Stop, Hide (A) - Animations can be paused **Seizures and Physical Reactions:** - ✅ 2.3.1 Three Flashes or Below Threshold (A) - No flashing content **Navigable:** - ✅ 2.4.1 Bypass Blocks (A) - Skip links provided - ✅ 2.4.2 Page Titled (A) - Descriptive page titles - ✅ 2.4.3 Focus Order (A) - Logical focus order - ✅ 2.4.4 Link Purpose (In Context) (A) - Clear link text - ✅ 2.4.5 Multiple Ways (AA) - Navigation + search + sitemap - ✅ 2.4.6 Headings and Labels (AA) - Descriptive headings - ✅ 2.4.7 Focus Visible (AA) - Clear focus indicators (2px) - ✅ 2.4.11 Focus Not Obscured (Minimum) (AA) - WCAG 2.2 NEW **Input Modalities:** - ✅ 2.5.1 Pointer Gestures (A) - No complex gestures required - ✅ 2.5.2 Pointer Cancellation (A) - Actions on up-event - ✅ 2.5.3 Label in Name (A) - Visible label matches accessible name - ✅ 2.5.4 Motion Actuation (A) - No motion-only input - ✅ 2.5.7 Dragging Movements (AA) - WCAG 2.2 NEW - Alternatives to dragging - ✅ 2.5.8 Target Size (Minimum) (AA) - WCAG 2.2 NEW - 24x24px (we use 44x44px)Understandable (21 criteria) - 100% compliant
**Readable:** - ✅ 3.1.1 Language of Page (A) - Page language declared - ✅ 3.1.2 Language of Parts (AA) - Language changes marked **Predictable:** - ✅ 3.2.1 On Focus (A) - Focus doesn't trigger context changes - ✅ 3.2.2 On Input (A) - Input doesn't cause unexpected changes - ✅ 3.2.3 Consistent Navigation (AA) - Navigation consistent across pages - ✅ 3.2.4 Consistent Identification (AA) - Components labeled consistently - ✅ 3.2.6 Consistent Help (A) - WCAG 2.2 NEW - Help access consistent **Input Assistance:** - ✅ 3.3.1 Error Identification (A) - Errors clearly identified - ✅ 3.3.2 Labels or Instructions (A) - Form fields have labels - ✅ 3.3.3 Error Suggestion (AA) - Helpful error messages - ✅ 3.3.4 Error Prevention (AA) - Confirmation for legal/financial actions - ✅ 3.3.7 Redundant Entry (A) - WCAG 2.2 NEW - Auto-fill repeated info - ✅ 3.3.8 Accessible Authentication (Minimum) (AA) - WCAG 2.2 NEW - No cognitive testsRobust (3 criteria) - 100% compliant
**Compatible:** - ✅ 4.1.2 Name, Role, Value (A) - Proper ARIA usage - ✅ 4.1.3 Status Messages (AA) - ARIA live regions for updates✅ Automated accessibility scanning (axe-core 4.10, pa11y, Lighthouse)
✅ Manual keyboard navigation testing (Tab, Shift+Tab, Enter, Escape)
✅ Screen reader testing (NVDA, JAWS, VoiceOver, TalkBack)
✅ Color contrast analysis (WCAG Contrast Checker, manual verification)
✅ User testing with community members (ongoing)
✅ Mobile device testing (iOS Safari, Android Chrome)
✅ Browser testing (Chrome, Firefox, Safari, Edge)
Continuous Monitoring:
- GitHub Actions CI/CD runs axe-core on every commit
- Weekly full-site accessibility scans (15 pages)
- Monthly manual audits by accessibility team
- Quarterly community feedback reviews
✅ W3C HTML5 Valid
- Semantic HTML5 elements used throughout (nav, main, header, footer, article, section)
- Proper DOCTYPE declaration and character encoding (UTF-8)
- Valid attribute usage and element nesting
- No parsing errors that affect assistive technology
✅ W3C CSS3 Valid
- Modern CSS3 features (Grid, Flexbox, Custom Properties)
- Valid syntax throughout all stylesheets
- 66+ media queries supporting user preferences (reduced-motion, color-scheme, contrast)
- No deprecated properties or syntax errors
View Current Limitations & Progress
### Current Limitations:
**Third-Party Content:**
- Some embedded social media widgets (Facebook, Twitter) may not meet our standards
- Working with platforms to improve accessibility
- Always provide text alternatives
**Legacy Content:**
- Some older blog posts from 2024 may have minor accessibility issues
- Active audit and remediation project ongoing
- All new content fully accessible from October 2025 onward
**PDF Documents:**
- Not all downloadable PDFs are fully tagged/accessible yet
- Priority: Legal templates and guides (completed)
- Ongoing: Blog post PDFs, resource downloads
- Timeline: 100% accessible PDFs by Q1 2026
**Dynamic Features:**
- Some JavaScript-powered features require JavaScript enabled
- Fallbacks provided for critical functionality (forms, navigation)
- Progressive enhancement approach ensures basic access
**Browser Compatibility:**
- Optimized for modern browsers (Chrome, Firefox, Safari, Edge)
- Limited testing on IE11 (end of life, <1% usage)
- Mobile browsers fully supported
### In Progress:
**Q4 2025:**
- ✅ Complete PDF accessibility remediation
- ✅ Third-party widget alternatives
- ✅ Legacy blog post audit (50% complete)
**Q1 2026:**
- 🔄 Independent third-party AODA/ACA audit
- 🔄 VPAT (Voluntary Product Accessibility Template) publication
- 🔄 Enhanced screen reader optimization
**Reporting Issues:**
If you encounter any barrier, even if listed here, **please report it**. Your specific use case helps us prioritize fixes.
**[Report Accessibility Barrier →](/contact?subject=Accessibility+Barrier)**
⚙️ Accessibility Settings - Customize your preferences
→
🚶 Accessibility Walkthrough - Guided tour
→
📖 User Guide - Complete documentation
→
🗺️ Roadmap - Planned improvements
→
✨ Features - See all features
→
### Legal & Privacy
🔒 Privacy Policy - Data protection
→
📄 Terms of Service - Accessibility commitments
→
👥 Community Guidelines - Inclusive standards
→
📧 Contact - Get in touch
→
---
**Last updated**: October 08, 2026
*3mpwrApp - Accessibility First, Always.* ♿💚
💬 Was this page helpful?