Accessibility Statement

DRAFT — pending owner confirmation. The conformance statements below must be re-verified after every significant change.

Last updated: 2026-10-08

We want everyone to be able to use iambeep.com, including people who use screen readers, keyboards, voice control, magnification or high-contrast settings. Our target is WCAG 2.2 Level AA.

What we have done

• Every page has a skip-to-content link, a single main landmark, and a logical heading order.
• All sign-in, sign-up and account forms use real labels, correct autocomplete values (username, current-password, new-password, one-time-code), and error messages announced to screen readers.
• Signing in never requires solving a puzzle, transcribing characters or recalling a memorized pattern (WCAG 2.2 SC 3.3.8). You can paste passwords and use a password manager, passkey or authenticator app.
• Everything works with a keyboard alone, with a visible focus indicator.
• Text and interface colors meet AA contrast in both the light and dark themes. Motion is reduced if your system asks for it.
• Images that convey information have text alternatives.

Known limitations

[[OWNER: after each accessibility test run, list any remaining issues here with their status. At the time of writing, automated testing (axe-core) and a manual keyboard pass are recorded in COMPLIANCE.md.]]

• The embedded payment form is provided by Stripe; its accessibility is Stripe's responsibility, though we test that the surrounding steps work with a keyboard and screen reader.
• Some benchmark code samples on pricing pages are long and scroll horizontally.

Feedback and help

If something is hard to use, tell us: odhamhendrix@gmail.com [[OWNER: confirm]]. Say which page and what assistive technology you use, and we will reply within 5 business days with a fix or an alternative way to get what you need. You can also use the privacy request form if you prefer a form.