Accessibility

Last reviewed: April 13, 2026

We aim for WCAG 2.2 AA on public pages and core product flows. Key routes are checked in CI with automated axe audits and keyboard-navigation tests. We use semantic HTML, visible focus states, and responsive layouts as baseline requirements.

1. What we test

2. Known limitations

Some third-party widgets, such as CAPTCHA or payment flows, can have accessibility limits outside our control. If a control blocks you, we want to know.

3. Feedback

Email contact@adpena.com with the page URL, what happened, and the browser or assistive technology you used.