Accessibility
AidNow treats accessibility as a safety requirement, not a compliance checkbox.
Our approach
If a person with shaking hands, poor eyesight, a cheap phone, or a screen reader cannot use the emergency interface, the design has failed. Accessibility is not an optional enhancement — it is part of whether guidance can be used when it matters.
Who we design for
- People currently experiencing an emergency (scared, injured, shaking)
- Older adults who may have vision or dexterity challenges
- Children who may be the only person able to help
- People with low literacy or limited formal education
- People with disabilities (visual, motor, cognitive)
- People using inexpensive phones with small screens
- People with poor or no internet connection
- People who speak Hindi or regional languages
What we do
- Large touch targets
- Minimum 48px (WCAG 2.2), 64px for emergency actions
- High contrast
- Emergency instructions meet AAA contrast ratios where possible
- Plain language
- No medical jargon required to find or use guidance
- Keyboard navigation
- Full keyboard support with visible focus indicators
- Screen reader support
- Semantic HTML, ARIA landmarks, aria-live regions
- Offline access
- Critical emergency scenarios cached for use without internet
- Skip navigation
- Skip-to-content link on every page
- Reduced motion
- Respects prefers-reduced-motion
- No auto-play
- No automatic audio or video
- Readable typography
- Minimum 16px base, 18px+ for emergency instructions
Current limitations (honest)
- Full WCAG 2.2 AA audit not yet completed
- Hindi locale accessibility features are incomplete
- Manual screen reader testing (NVDA, VoiceOver, TalkBack) is documented but not yet executed
- Dark mode in emergency pages uses a fixed high-contrast scheme
- Some color contrast measurements are pending formal verification
- Decision tree keyboard navigation needs improvement
Report an accessibility issue
If you encounter an accessibility barrier on AidNow, please let us know. Describe the page, the barrier you hit, and what assistive technology or device you were using if applicable.
Standards we are working toward
WCAG 2.2 Level AA. We test with: 36 automated accessibility tests, documented manual testing checklists, and semantic HTML structure audit.
Manual testing areas documented in our accessibility audit include screen reader navigation, real-device touch usability, color contrast verification, keyboard-only navigation, reduced motion preferences, offline PWA behaviour, print accessibility, and visual instruction alt text review.
Related pages
In an emergency, call 112 (India) or your local emergency number.