Accessibility Excellence
Four pillars of WCAG 2.1 compliance ensuring inclusive digital experiences for all users
Perceivable
All information is presentable in ways users can perceive, with proper alt text, color contrast, and text alternatives.
Operable
Complete keyboard navigation, proper focus management, and user interface components that work for everyone.
Understandable
Clear information architecture, predictable functionality, and helpful error identification and correction.
Robust
Compatible with assistive technologies, valid markup, and reliable interpretation across diverse user agents.
📋 Compliance Overview
Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
1.1 Text Alternatives ✅ COMPLIANT
- All images include appropriate alt text
- Decorative images marked with aria-hidden="true"
- Complex graphics have detailed descriptions
- SVG elements include proper title and desc elements
1.3 Adaptable ✅ COMPLIANT
- Proper heading hierarchy (h1 → h2 → h3)
- Semantic HTML elements used correctly
- Form labels properly associated
- Content works in all orientations
1.4 Distinguishable ✅ COMPLIANT
- 4.5:1 contrast ratio for all text
- 3:1 contrast for UI components
- Text resizable up to 200%
- Content reflows at 320px width
Principle 2: Operable
User interface components and navigation must be operable by all users.
2.1 Keyboard Accessible ✅ COMPLIANT
- All functionality available via keyboard
- No keyboard traps present
- Custom keyboard shortcuts use modifiers
- Focus management for modal dialogs
2.4 Navigable ✅ COMPLIANT
- Skip links on all pages
- Descriptive page titles
- Logical tab order
- Clear focus indicators (3px solid #fbbf24)
2.5 Input Modalities ✅ COMPLIANT
- Simple click/tap interactions only
- Proper pointer cancellation
- Accessible names include visible labels
- No path-based gestures required
Principle 3: Understandable
Information and user interface operation must be understandable to all users.
3.1 Readable ✅ COMPLIANT
- HTML lang attribute set to "en"
- All content in English
- Clear, readable language throughout
- Consistent terminology
3.2 Predictable ✅ COMPLIANT
- No context changes on focus
- Consistent navigation across pages
- Components labeled consistently
- Predictable behavior throughout
3.3 Input Assistance ✅ COMPLIANT
- Form errors clearly identified
- Clear labels and instructions
- Error suggestions provided
- Error prevention for important actions
Principle 4: Robust
Content must be robust enough for interpretation by diverse user agents and assistive technologies.
4.1.1 Parsing ✅ COMPLIANT
- Valid HTML markup throughout
- No duplicate IDs
- Proper element nesting
- Complete start and end tags
4.1.2 Name, Role, Value ✅ COMPLIANT
- All UI components have accessible names
- Roles defined via semantic HTML and ARIA
- States and values programmatically determinable
- Properties and values can be set by user agents
4.1.3 Status Messages ✅ COMPLIANT
- Live regions for dynamic content
- Status changes announced to screen readers
- Progress updates communicated appropriately
- Error states properly announced
Testing Methodology
Automated Testing ✅
- axe-core accessibility scanner
- WAVE web accessibility evaluator
- Lighthouse accessibility audit
- Pa11y command line testing
Manual Testing ✅
- Keyboard navigation testing
- Screen reader testing (NVDA, JAWS, VoiceOver)
- Color contrast verification
- Mobile accessibility testing
User Testing ✅
- Assistive technology users feedback
- Cognitive accessibility review
- Motor impairment usability testing
- Vision impairment navigation testing
Contact & Support
Accessibility Support
Email: ask@personalinjurywhiz.com
Response Time: 48 hours for accessibility issues
Alternative Formats: Available upon request
Feedback Welcome
We continuously work to improve accessibility. Contact us with:
- The specific page or feature affected
- Assistive technology details (if applicable)
- Description of difficulty experienced