Accessibility Statement

Effective date: 23 May 2026 · Last updated: 23 May 2026

1. Our commitment

Amphora AI is committed to making am4a.ai accessible to all visitors, including those who use assistive technologies (screen readers, screen magnifiers, voice-control software, switch devices, keyboard-only navigation). We treat accessibility as a feature, not an afterthought.

2. Conformance target

This website is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG 2.1 AA is the standard referenced by:

• Americans with Disabilities Act (ADA), Title III — U.S. Department of Justice guidance and the precedent set by Robles v. Domino's Pizza (9th Cir. 2019).
• European Accessibility Act (EAA) — enforceable across EU member states since 28 June 2025.
• EN 301 549 — the EU's harmonized standard, which references WCAG 2.1.
• Section 508 of the U.S. Rehabilitation Act — for federal procurement contexts.
• California Unruh Act, NY State Human Rights Law, AODA (Ontario), and several other state and provincial statutes that extend ADA-style protections.

3. What this means in practice

Specific accessibility features built into am4a.ai:

• Keyboard-only navigation works for every interactive control (header, hero, modals, footer, legal pages). The cookie consent banner traps focus while open and is dismissible with Escape.
• Skip-to-main-content link appears as the first Tab stop on every page (WCAG 2.4.1).
• Semantic landmarks — <header role="banner">, <main>, <footer role="contentinfo"> — for screen-reader navigation.
• Form inputs have explicit programmatic labels (WCAG 1.3.1 / 3.3.2). Required fields are marked with aria-required="true".
• Icon-only buttons carry aria-label announcements (WCAG 4.1.2).
• Visible focus indicators on every interactive element with at least 3:1 contrast (WCAG 2.4.7).
• prefers-reduced-motion respected — the particle-network background animation is paused for visitors with vestibular accommodation enabled (WCAG 2.3.3).
• Color contrast — body text + interactive elements meet at least 4.5:1 against their backgrounds; large text and UI components meet at least 3:1 (WCAG 1.4.3 / 1.4.11).
• Resizable text — text scales to 200% without loss of content or function (WCAG 1.4.4).
• HTML lang attribute set on every page so screen readers use the correct pronunciation engine (WCAG 3.1.1).
• Page titles are unique and descriptive (WCAG 2.4.2).
• Iframes (e.g., the knowledge-graph visualization) carry descriptive title attributes (WCAG 4.1.2).

4. Known limitations

We test the site against WCAG 2.1 AA continuously, but no site is ever fully done. Currently-known limitations:

• The Pac-Man minigame (launched from the homepage) is a visual game by nature and is not designed for screen-reader use. It is hidden from keyboard tab order when not active.
• The embedded knowledge-graph visualization is a WebGL canvas. The canvas itself does not expose structured graph content to assistive technologies (the underlying data is also not exposed publicly). We are evaluating an accessible textual alternative for a future release.
• We are progressively migrating toward WCAG 2.2 conformance — specifically 2.5.8 Target Size (Minimum) (24×24 CSS pixels) and 2.4.11 Focus Not Obscured.

5. Assistive technology compatibility

We test against the following combinations regularly:

• VoiceOver on iOS (Safari) — current iOS major and previous
• VoiceOver on macOS (Safari) — current macOS major and previous
• NVDA on Windows (Firefox, Chrome) — current and previous
• JAWS on Windows (Chrome, Edge) — current
• TalkBack on Android (Chrome) — current
• Keyboard-only navigation in all major browsers

6. Report a barrier

If you encounter content or functionality on am4a.ai that is difficult or impossible to use, please tell us. We treat accessibility barriers as bugs, not feature requests.

Email info@am4a.ai with the subject "Accessibility" and please include:

• The URL of the page where you experienced the issue
• The assistive technology you were using (if any), and your operating system + browser
• A description of what didn't work — even a one-line "the Subscribe button didn't announce to my screen reader" is enough for us to act

We aim to acknowledge accessibility reports within 2 business days and to resolve confirmed barriers within 10 business days for production-blocking issues, longer for design-level changes that need broader rework.

7. Enforcement procedures

If you are not satisfied with our response to an accessibility complaint:

• United States — you may file a complaint with the U.S. Department of Justice Civil Rights Division, or with your State Attorney General.
• European Union — your member state designates a market-surveillance authority under the EAA; the European Commission maintains a list of national authorities.
• United Kingdom — you may file with the Equality and Human Rights Commission.
• Other jurisdictions — your national or regional equality / accessibility authority is the appropriate channel.

8. Technical conformance details

This statement was prepared on 23 May 2026 using a self-assessment combined with automated tooling (axe-core, Lighthouse) and manual screen-reader testing. We do not currently hold a formal third-party conformance audit — when we do, this section will link to it.

The statement is based on the following accessibility standards:

• W3C Web Content Accessibility Guidelines 2.1
• EN 301 549 V3.2.1 (2021-03)
• U.S. Section 508 / 36 CFR Part 1194 Appendix A

Conformance claim: partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that most parts of the content fully conform, except for the items called out in Section 4 above.

9. Updates to this statement

We update this statement whenever we ship a change that materially affects accessibility — either fixing a known limitation or introducing a new feature. The "Last updated" date at the top of the page reflects the most recent change.

10. Contact

Amphora AI — accessibility contact: info@am4a.ai