Accessibility

App approach

• Use native controls and system text, authentication, notification, camera, photo, file, speech, and haptic mechanisms where practical.
• Keep labels and status available without relying only on color, and maintain touch targets suited to the device.
• Design and test common tasks for system text sizing, VoiceOver labels, reduced motion, increased contrast, and Voice Control where the platform and layout allow.
• Keep Apple Watch flows short, with clear status and a focused action rather than duplicating the full iPhone interface.

Website support

• Semantic headings, landmarks, lists, link names, and a keyboard skip link organize the pages.
• Keyboard focus is visible, controls have accessible names, and content does not require hover.
• English and Russian can be selected explicitly, and the document language updates with the selection.
• Motion is reduced when the operating system requests reduced motion; the legal and support content remains usable on narrow screens.

App Store accessibility disclosures

Apple's Accessibility Nutrition Labels are feature claims for every common task on each supported device. GrantTap will publish only labels verified against the release build on iPhone and Apple Watch. This page describes the design approach; it is not a claim that every Apple accessibility criterion has already been independently audited.

Report an accessibility barrier

Email support with the device and model, iOS or watchOS version, GrantTap version, accessibility feature in use, expected result, and the shortest sequence that reproduces the barrier. A screen recording or screenshot can help after all private task content and paths are removed.

Never send a pairing token, encryption key, real approval payload, repository secret, or confidential prompt. Accessibility reports are handled as support correspondence under the Privacy Policy.