Built for access
The interface uses semantic headings and landmarks, visible focus, labelled fields, keyboard-operable menus, meaningful alternative text, responsive layouts, sufficient contrast, and reduced-motion support.
Need another format?
If content or a process is difficult to use, contact the foundation by phone or WhatsApp. We will work toward an accessible alternative without asking for unnecessary personal information.
Ongoing review
Automated checks support but do not replace testing with people using assistive technology. Issues should be logged, prioritised, retested, and documented.
Forms and error recovery
Forms should identify required fields, explain errors in text, preserve useful input where safe, and announce submission results to assistive technology. Sensitive information should not be requested in a general contact form when a protected workflow is available.
Images, motion and language
Images require meaningful alternative text when informative and empty alternatives when decorative. Motion should respect reduced-motion preferences and avoid blocking access to content. English and Tamil interfaces should keep navigation and essential instructions understandable in both languages.
Report a barrier
Describe the page, task, device or assistive technology involved and the format that would help. Do not include passwords or private assistance documents. The final statement will publish an approved response route and review date.