ApeBot.ioLog InGet ApeBotAccessibility Statement
Updated October 8, 2026
Our accessibility target
We aim to make ApeBot.io usable with a keyboard and assistive technologies, using WCAG 2.2 Level AA as an engineering target. We have not completed an independent conformance audit and do not claim certified ADA or worldwide compliance.
Features available
Skip-to-content navigation, semantic headings, labeled forms, visible keyboard focus, responsive layouts, gallery pause controls, reduced-motion handling, and native modal image previews are implemented. Modal dialogs support Escape and return focus after closing. Password fields allow paste and password managers. You can stop gallery animation through the footer's Reduce motion control.
Known limitations
Template and chart images are visual previews; their captions describe the interface but do not fully transcribe every value in the screenshot. New language strings can fall back to English until reviewed translations are added. Third-party payment and challenge interfaces require their own accessibility assessment. Authenticator enrollment and account recovery need manual assistive-technology review. Color contrast, zoom/reflow, focus order, errors and all authenticated screens must be audited regularly.
Report a barrier
Use /privacy-center and select Accessibility assistance without signing in, or use Dashboard → Support. Tell us the page, the task you were trying to complete and, optionally, the assistive technology you use. Do not include credentials or medical information. Administrators receive a tracked request and should offer an accessible alternative. We target an initial response within 28 days and review urgent access barriers sooner.
Review
The administrator compliance calendar tracks accessibility testing and remediation. WCAG alignment is useful evidence; it does not itself determine legal coverage under the ADA, the European Accessibility Act, or other local laws.