OneTap accessibility statement
Draft for legal review. Not yet published. Counsel and Oltin must review this statement, and complete every part in square brackets, before OneTap goes live.
Our aim
Everyone at a company that uses OneTap should be able to check in, see their attendance and manage their team, whatever their abilities and whatever device they use.
The standard we build to
OneTap is built to meet WCAG 2.1 level AA, the level India's IS 17802 asks for. This statement covers the OneTap app on iPhone and Android, and OneTap Admin in a web browser.
How we check it
- Every change is tested before it is released: colour contrast in light and dark themes, and every screen of the app for labels, roles, touch targets of at least 44 points, text that grows with the phone's text size, and a heading on every screen.
- Before launch, and before each release that changes a screen, people check by hand with VoiceOver and TalkBack, the largest text sizes, keyboard-only use and 200% browser zoom. [Result of the launch check, and its date.]
What we know isn't accessible yet
[What the launch check finds that is not yet fixed, with when each will be.] Downloaded reports open in your own spreadsheet or PDF reader, whose accessibility we don't control; every report is also available as a spreadsheet.
Tell us about a barrier
If something in OneTap stops you or your people from using it, write to support@oltin.ai. Tell us the screen, what you were trying to do, and the device and assistive technology you use. We reply within 5 working days, and offer another way to do the task while we fix it.
If you aren't satisfied with our reply, you can complain to the Chief Commissioner for Persons with Disabilities under the Rights of Persons with Disabilities Act, 2016.
About this statement
We review this statement after every manual check, and at least once a year. See also the OneTap trust center.