Accessibility statement

We want everyone to be able to use APInguin, including people who use a screen reader, a keyboard instead of a mouse, magnification, voice control or other assistive technology. Accessibility is part of how we build and review every page, not a widget added on top.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That target also covers WCAG 2.1 AA (used by the European standard EN 301 549), WCAG 2.0 AA (the basis of Israeli Standard IS 5568) and the WCAG-based guidelines used across Latin America.

APInguin is partially conformant with WCAG 2.2 AA: we are reviewing the site page by page and fixing what we find, starting with the public pages. What we build in:

• A "Skip to main content" link at the top of every page.
• Keyboard operation with a visible focus indicator on interactive controls.
• Text labels on buttons, links, form fields and images for screen readers.
• Animations that stop when your device is set to reduce motion.
• Light and dark themes in the app.
• An accessibility menu (the round button, or the icon in the app's top bar) for larger text, higher contrast, underlined links and stopping animations. It is a convenience: the site works without it.
• No accessibility overlay or plugin: fixes are made in the site itself.

• Charts and score dials in the app may not yet describe every value to screen readers. The same numbers are shown as text in the findings list and the downloadable report.
• Per-scan audit PDFsare not tagged for screen readers (brand, creator and industry reports are produced as tagged PDF/UA documents). On request we will send any report's content in an accessible format.
• Custom workspace colors chosen by a workspace admin may not always meet contrast guidelines.
• Third-party content we display as scan evidence (videos, posts and screenshots from other platforms) is outside our control and may not be accessible.

Automated accessibility checks cover our public pages and the main screens of the app, in light and dark mode, and we review new screens with a keyboard. A full review with the NVDA and VoiceOver screen readers is in progress. This statement was last reviewed on the date shown above.

If any part of APInguin is hard to use, or you need information in a different format, email support@apinguin.comwith the subject "Accessibility". Tell us the page, what you were trying to do, and the browser and assistive technology you use if you can.

A person on our team will reply within five business days. Until a problem is fixed, we will help you get the same result another way, for example by running a scan for you and sending the report in a format that works for you.