Accessibility Statement

Last updated: 4 May 2026

1. Our Commitment

AI Central Tools is committed to making our platform accessible to as many people as possible, regardless of ability or assistive technology. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, which is the technical standard required by the EU European Accessibility Act 2025 (Directive 2019/882), the UK Public Sector Bodies Accessibility Regulations, and US Section 508.

2. Conformance Level

AI Central Tools is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means some parts of the content do not yet fully meet the accessibility standard. We disclose known limitations in §6 below and have a remediation roadmap.

3. Accessibility Features Implemented

Across all 330 tools, the marketplace, blog, and account dashboard we have implemented:

Skip to content link as the first focusable element on every page (WCAG 2.4.1 Bypass Blocks).
Semantic landmarks (<header>, <nav>, <main>, <footer>) with ARIA labels (WCAG 1.3.1 Info and Relationships).
Keyboard navigation for all interactive elements including the mobile menu (focus trap, ESC dismissal, arrow-key roving focus on tabs) — WCAG 2.1.1 Keyboard.
Visible focus indicators (:focus-visible 2px outline at AA-compliant contrast against background) — WCAG 2.4.7 + 2.4.11 Focus Not Obscured (new in WCAG 2.2).
Color contrast verified at minimum 4.5:1 for body text, 3:1 for large text and graphical elements — WCAG 1.4.3 + 1.4.11.
Form labels programmatically associated with every input (<label for> or aria-label) — WCAG 1.3.1 + 4.1.2.
Alt text auto-generated and reviewable for all images (provided by our Alt Text Generator tool) — WCAG 1.1.1.
Heading hierarchy follows logical document outline (no h1→h3 skips) — WCAG 1.3.1.
prefers-reduced-motion media query respected: marquee, rotating placeholder, and parallax effects pause for users who request reduced motion — WCAG 2.3.3.
Language declaration on the <html lang> element + per-section overrides for translated content (19 languages) — WCAG 3.1.1 + 3.1.2.
Tap targets minimum 44 × 44 CSS pixels on touch devices — WCAG 2.5.5 (was AAA in 2.1, AA in 2.2 via 2.5.8 Target Size Minimum).
Resize text up to 200% without loss of content or functionality — WCAG 1.4.4.
Zoom and reflow support — content reflows at 320 CSS pixels wide without horizontal scrolling — WCAG 1.4.10.
Cookie consent banner keyboard accessible with proper ARIA roles and labels — WCAG 2.1.1 + 4.1.2.

4. Compatibility With Browsers and Assistive Technology

AI Central Tools is designed to be compatible with the following assistive technologies:

Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS + iOS), TalkBack (Android)
Browsers: Chrome ≥ 100, Firefox ≥ 100, Safari ≥ 15, Edge ≥ 100 (covers ~98% of global usage)
Operating systems: Windows 10/11, macOS Big Sur+, iOS 15+, Android 11+
Voice control: macOS Voice Control, Dragon NaturallySpeaking, Windows Speech Recognition
Browser zoom: tested up to 400% with no functional loss

5. Technical Specifications

Accessibility relies on the following technologies to work with the particular combination of web browser and any assistive technology installed on your computer:

HTML5 (semantic elements + ARIA where native semantics insufficient)
CSS3 (uses :focus-visible, prefers-reduced-motion, prefers-color-scheme)
JavaScript (progressive enhancement — core navigation works without JS)
WAI-ARIA 1.2 (used sparingly; native HTML preferred)
SVG (decorative SVG marked aria-hidden, informative SVG has accessible names)

6. Known Limitations

Despite our best efforts, the following content currently has known accessibility limitations. We are working to remediate each of these — see §9 for the roadmap.

Stripe Checkout iframe — third-party payment iframe is provided by Stripe and we cannot directly modify its accessibility. Stripe states their checkout meets WCAG 2.1 AA (stripe.com/docs/security/accessibility).
Embedded YouTube/Vimeo videos in blog posts — captions depend on the video uploader. We require captions for our own videos but cannot guarantee third-party embeds.
Auto-generated alt text on legacy images (~3% of corpus) — alt text is being backfilled by our cron job (~10 images/cycle); 9,800 still in queue.
Some translated UI strings may have minor punctuation/spacing differences from the source English (4% of strings flagged for review across 19 languages).
Captcha on sign-up — Cloudflare Turnstile is the primary anti-bot system; an audio fallback exists for screen-reader users.

7. Audit Date and Methodology

This statement was prepared on 4 May 2026 following an automated and manual audit of all major surfaces.

Tooling: axe-core 4.x (via Playwright), Lighthouse 11 accessibility audits, manual screen-reader walkthrough with NVDA + VoiceOver
Surfaces audited: Homepage, Tools index, sample tool detail pages (Content Rewriter, Blog Topic Generator), Pricing, Find a Tool, Marketplace, Workflow detail, Testimonials, Roadmap, Status, Account dashboard, Register, Login, Privacy, Terms
Standard: WCAG 2.2 Level AA (covers WCAG 2.0 AA + 2.1 AA + 2.2 AA new criteria including 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size Minimum, 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication)
Continuous regression: axe-core runs in our Playwright CI on every deploy and fails the build on critical/serious violations
Next scheduled review: 4 November 2026

8. Feedback and Contact Information

We welcome your feedback on the accessibility of AI Central Tools. If you encounter accessibility barriers, please contact us:

Email: [email protected] (we aim to respond within 2 business days)
Contact form: aicentraltools.com/contact/
Subject line: [Accessibility] followed by the page URL and the issue
Preferred languages: English, Czech, German (other languages also welcome — we use translation tooling)

9. Remediation Roadmap

We track accessibility issues in our public issue tracker. Active items as of 4 May 2026:

Q2 2026: Backfill alt text for the remaining 9,800 legacy images (running)
Q2 2026: Add captions to all marketing videos (in progress)
Q3 2026: Replace Cloudflare Turnstile with hCaptcha audio fallback as primary (planned)
Q3 2026: Re-audit translated UI strings across all 19 languages (planned)
Q4 2026: Annual third-party accessibility audit by an external WCAG specialist (planned)

10. Enforcement Procedure

Users in the European Union are entitled, under the European Accessibility Act 2025 (Directive 2019/882), to escalate unresolved accessibility complaints to their national enforcement body. In the Czech Republic, this is the Ministry of Labour and Social Affairs (MPSV). In the United States, complaints may be filed with the U.S. Department of Justice ADA or Title III mechanisms.

11. Formal Approval

This accessibility statement was approved by the AI Central Tools team on 4 May 2026 and is reviewed at minimum every six months, or whenever a substantial release affects the user interface.

Questions about this accessibility statement? Contact us · [email protected]

Phase 12 — newer surfaces (WCAG 2.1 AA)

Daily heuristic scan over 44 newer surfaces (top 25 tools, 7 persona pages, /api/docs/, /api/webhooks/, /agents/, /pricing/ light + dark, /docs/). Each surface is graded against the WCAG 2.1 AA checklist; an issue is recorded if any check fails.

P0 — critical (blocking): 0
P1 — serious: 24
P2 — moderate: 0
P3 — minor (cosmetic): 42

No P0 blocking issues. The remaining P1–P3 findings are tracked in our roadmap and addressed on a rolling basis (see §9 below).