Version 1.0 | Effective 21 Nov 2024 | Last Reviewed 11 Apr 2025 | Prepared by Privacy & Compliance Office, AtomLeap.ai
1. Our Commitment to Accessibility
AtomLeap.ai aims to ensure its platform and services remain inclusive and accessible to all users, regardless of abilities or disabilities. The organization recognizes digital accessibility as both a legal requirement and ethical obligation supporting its innovation mission.
The company believes every user deserves barrier-free technology access and has established a continuous improvement framework to maintain and enhance accessibility throughout its service delivery lifecycle.
2. Accessibility Principles We Follow
The accessibility strategy follows four core principles:
- Perceivable: Information and UI components must be presented in ways users can perceive
- Operable: Interface components and navigation must be usable via keyboard, screen reader, or voice input
- Understandable: Content must be clear and predictable, with error feedback and user-friendly instructions
- Robust: Content must be compatible with current and future assistive technologies and user agents
These principles are incorporated across product design, engineering, QA, and documentation processes.
3. Standards and Guidelines
The organization designs services according to:
- WCAG 2.1 Level AA by the World Wide Web Consortium (W3C)
- The Rights of Persons with Disabilities Act, 2016 (India)
- Section 508 of the Rehabilitation Act (U.S.)
- EN 301 549 for ICT Accessibility (European Union)
- ISO/IEC 40500:2012 (international standard for WCAG 2.0)
- Best practices from Microsoft Inclusive Design, WAI-ARIA, and Apple HIG
4. Platform Accessibility Features
Built-in accessibility features include:
- Skip navigation and tab indexing for keyboard users
- High-contrast and dyslexia-friendly color modes
- Responsive scaling of text and interface for low-vision users
- Text alternatives (alt text) for all images, icons, and logos
- Role-based ARIA landmarks and labels for screen readers
- Voice command and speech input recognition (where supported)
- Closed captions for embedded videos and podcasts
- Resizable input fields and tooltips for clarity
- Accessible error handling and inline validation in forms
5. Accessibility Testing Procedures
The organization conducts regular audits using automated and manual tools. QA and compliance teams:
- Run weekly automated scans using Axe, Lighthouse, and Wave
- Conduct monthly keyboard-only navigations
- Manually test assistive compatibility with NVDA, VoiceOver, and TalkBack
- Validate contrast and readability with browser plugins
- Include accessibility testing in CI/CD pipelines
- Maintain test reports, recommendations, and remediation logs
The roadmap prioritizes accessibility bugs alongside security and performance issues.
6. Employee and Stakeholder Training
The organization invests in accessibility awareness through:
- Onboarding modules for inclusive design and WCAG principles
- Monthly webinars on digital inclusion and user empathy
- Toolkits for content creators and developers
- Quarterly accessibility review meetings with stakeholders
- Community feedback sessions to co-design solutions with real users
The company collaborates with accessibility consultants and organizations for benchmarking.
7. Known Accessibility Gaps
Current limitations under remediation include:
- Third-party widgets (e.g., maps, calendars) may lack ARIA compatibility
- Auto-generated transcripts may have inaccuracies
- User-generated content may not always meet standards
- Legacy blog posts may lack semantic structure or alt text
Resolution milestones appear in Appendix B.
8. Assistive Technology Compatibility
The platform is compatible with:
- Screen Readers: JAWS, NVDA, VoiceOver, ChromeVox, Orca
- Magnifiers: Windows Magnifier, ZoomText
- Voice Input: Dragon NaturallySpeaking, macOS Voice Control
- Devices: Braille displays, overlays, smart readers
Testing covers major browsers, operating systems, and device types (desktop, mobile, tablet).
9. Accessibility Governance and Compliance
An internal Accessibility Task Force oversees:
- The Accessibility Policy (Appendix A)
- Tracking KPIs (defect resolution, user feedback)
- Legal compliance monitoring
- Quarterly reporting to leadership
- Coordinating third-party audits
10. Feedback and Support
For accessibility issues, contact:
- Email: accessibility@atomleap.ai
- Phone: +91 905 906 9922 (Mon–Fri, 10:00–18:00 IST)
- Address: Accessibility Coordinator, AtomLeap.ai, Unit No. 12A04, 13th Floor, Manjeera Trinity Corporate, KPHB Phase 3, Kukatpally, Hyderabad, Telangana, India
The organization responds within 5 business days, with alternate formats provided within 15 days where feasible.
11. Continuous Improvement and Roadmap
- Quarterly inclusive design system reviews
- Annual public statement updates and scorecards
- Accessibility assessments for all new features
- Internal "Accessibility Guilds" to build champions
- Participation in GAAD and community outreach
Appendix A – Accessibility Policy Summary
- All new content must meet WCAG 2.1 Level AA
- Accessibility checks are required for all releases
- Clear feedback/reporting channels are provided
- Vendor selection includes accessibility review
- Inclusive language is enforced across UI/UX
Appendix B – Accessibility Roadmap & Timeline
- Q1: Launch audit + retroactive alt text tagging
- Q2: Enable high-contrast toggle and keyboard overlays
- Q3: Update legacy documents to accessible PDFs
- Q4: Conduct external WCAG 2.2 compliance audit
Appendix C – Glossary of Accessibility Terms
| Term | Definition |
|---|---|
| WCAG | Web Content Accessibility Guidelines by W3C |
| Screen Reader | Software that reads digital content aloud for visually impaired users |
| ARIA | Accessible Rich Internet Applications attributes for assistive tech |
| Alt Text | Descriptive text that replaces images for screen readers |
| Semantic HTML | Structured HTML using correct tags like <nav>, <main>, etc. |
| Contrast Ratio | The luminance difference between text and background color |
| Focus Indicator | Visual outline showing the currently selected element via keyboard |