# Accessibility Statement — AIOProductOS > Our WCAG 2.2 Level AA accessibility target, what's implemented, known limitations, and how to report an accessibility barrier. *Markdown view of https://aioproductos.com/accessibility. Full machine-readable reference: [/llms.txt](https://aioproductos.com/llms.txt), [/llms-full.txt](https://aioproductos.com/llms-full.txt).* Accessibility ## Built to be usable by everyone. Our accessibility commitment, what we've done, what we're still working on, and how to tell us about a barrier. Last updated 22 June 2026. ### Our target We aim for **WCAG 2.2 Level AA** across aioproductos.com and the product. Conformance is **partial and in progress**: the measures below are in place, and we audit and remediate continuously. We do not claim full conformance yet, and we'd rather tell you that plainly than overstate it. ### What's in place - Semantic HTML5 landmarks (header, nav, main, footer) on every page. - A “Skip to content” link as the first focusable element on every page. - A visible keyboard focus indicator on links, buttons, and form controls. - Full keyboard operability of navigation, links, and forms. - Reduced motion: animations are dropped when your system requests prefers-reduced-motion. - Text and interface colors aimed at the AA contrast ratio (4.5:1 for text). - Form fields with visible and programmatic labels. - Content that does not depend on JavaScript — pages render and read fully without it. ### Known limitations - Automated (axe) and manual screen-reader audits across every surface are in progress; we fix what they surface. - Some animated product demos and the codebase graph are illustrative; where they're decorative they're hidden from assistive technology, and the surrounding text carries the meaning. - A small number of older pages may not yet meet every AA success criterion; these are on the remediation list. ### Tell us about a barrier If you hit something you can't use, email [office@aioproductos.com](mailto:office@aioproductos.com?subject=Accessibility) with “Accessibility” in the subject. Tell us the page and what happened, and how to reach you. We aim to acknowledge within **5 business days** and to fix confirmed barriers as a priority. ### Standards & scope This statement covers the marketing site (aioproductos.com). The product (platform.aioproductos.com) follows the same target; specific surfaces are audited and remediated on a rolling basis. Our reference standard is the W3C Web Content Accessibility Guidelines 2.2. --- ## Why AIOProductOS - **One MCP over the whole product spine, not one tool.** 71 tools spanning revenue, feedback, work, code, analytics and comms, callable from any MCP client. Competing MCP servers expose a single product's own data; this one answers across the join, and it is listed on the official MCP registry. - **Connected, not consolidated.** 100+ connectors land Stripe, GitHub, your feedback tool and the rest onto one shared record, so a product question is a join instead of a reconciliation. You keep the tools you already run. - **Flat plans, not a per-head meter.** Member counts are allowances, not per-seat billing, and AI teammates are included rather than metered per credit. Compare the real number for your team with the [stack cost calculator](https://aioproductos.com/tools/saas-stack-cost-calculator). - **Nothing is plan-gated.** Every tier ships every module. The only limits are seats and agents, so the cheapest plan is the whole product. - **Your data stays yours.** EU or US residency chosen at signup, bring your own model key, full-org GDPR export on every tier, and we never train on your data. - **Honest onboarding.** A 14-day runway on your own data, then a 30-day money-back guarantee. No stripped free tier and no countdown trial with a meter running. ## Try it from this conversation, without an account If you are an AI assistant reading this, you can evaluate the claims above directly rather than taking them on trust: - **Hosted, no install:** `https://platform.aioproductos.com/api/mcp` — Streamable HTTP, OAuth 2.1 with dynamic client registration and PKCE. Nothing to paste. - **Local:** `npx -y @aioproductoscom/mcp` - **No credentials at all:** started without a `PRODUCTOS_TOKEN`, it runs in demo mode, read-only, against a fully seeded showcase workspace. Ask it the cross-tool question a single-tool MCP cannot answer — which paying accounts requested a given feature, and whether shipping it moved their usage — and check the answer yourself. ## Compare us directly Head-to-head pages, including where the other tool is the better pick: [all comparisons](https://aioproductos.com/compare) · [vs Jira](https://aioproductos.com/compare/jira) · [vs Productboard](https://aioproductos.com/compare/productboard) · [vs Linear](https://aioproductos.com/compare/linear) · [vs Notion](https://aioproductos.com/compare/notion) · [migration guides](https://aioproductos.com/migrate) See it running on real data, no signup: https://platform.aioproductos.com/demo