Accessibility

Last reviewed August 10, 2026

AP Control Labs aims to make its public website and customer console usable by people with disabilities. Accessibility is part of our release checks, but automated testing alone does not establish complete conformance or replace feedback from people using assistive technology.

What we test

Our continuous-integration checks scan key buying, documentation, trust, product, and sign-in pages at desktop and mobile viewport sizes. The checks use Axe rules tagged for WCAG 2.0 and 2.1 Level A and AA plus the available WCAG 2.2 AA rules, and also reject horizontal page overflow at the tested sizes.

Features currently supported

• Keyboard-visible focus indicators and a skip-to-content link
• Semantic headings, navigation labels, form labels, and status announcements
• Responsive layouts for public pages and documentation
• Text alternatives or accessible labels for interactive buying actions
• Contrast checks for text, links, controls, and code examples

Limits and ongoing work

Automated scans do not cover every assistive-technology combination, cognitive accessibility need, document supplied by a customer, or third-party destination such as RapidAPI, Smithery, Supabase, Stripe, or an MCP client. We will prioritize verified barriers in AP Control Labs interfaces and will document material improvements in the changelog.

Request help or report a barrier

Tell us the page or workflow, what you were trying to do, the browser or assistive technology involved, and the format or accommodation that would help. Do not include an API key, invoice, tax identifier, bank detail, or other sensitive customer content in the first message.

Accessibility feedback: apcontrollabs.support@gmail.com