Accessibility Statement

Our accessibility statement: the promise, the gaps, and how to reach us.

"Harnessing AI for a better human life." That sentence — written by our co-founder Jordan, who lives with profound vision and hearing loss — is the reason this page exists, and the reason it gets more care than the rest of our site combined. If our work doesn't reach every customer with dignity, the rest of what we do doesn't count.

Last reviewed: August 15, 2026 · Conformance target: WCAG 2.1 Level AA · Self-assessed.

Our commitment

Emaration LLC commits to making emaration.ai, every audit we deliver, and every membership deliverable usable by people with disabilities. That means people who use screen readers, switch devices, voice control, screen magnifiers, captioned audio, larger text, calmer motion, dyslexia-friendly fonts, or any combination of those.

We hold ourselves to WCAG 2.1 Level AA as the floor, and we work toward AAA where it doesn't cost the rest of the audience the experience. The accessibility drawer on this site (bottom-right) lets any visitor switch theme, contrast, font, size, motion, and request read-aloud — without asking permission and without losing their place.

If something on this page doesn't work the way it should, that's our problem, not yours. Tell us and we'll fix it.

Current conformance

Conformance level: emaration.ai is designed and self-assessed against WCAG 2.1 Level AA as of August 15, 2026. We have not yet engaged a third-party auditor. We will, and when we do, we'll publish that report on this page along with whatever they find — including the parts we got wrong.

Self-assessment is not a substitute for independent audit. We're being honest about that, because that's the deal: you trust us with your business; we tell you the truth about ours.

This page itself is built to AA. The features that make that possible are listed in the next section.

How we built this site to be accessible

Skip-to-main link as the first focusable element on every page.
Semantic landmarks: header, nav, main, footer, all with explicit roles or implicit ARIA.
Keyboard-only operable: every interactive control reachable and operable without a mouse. Focus is visible, never trapped except in the accessibility drawer (which closes on Escape).
Color contrast: automated checks verify the color tokens of every vibe-and-mode combination against WCAG AA — body text, links, button labels, focus rings, and the raised panel surfaces — and the High-Contrast vibe targets AAA. The honest edge of those checks is listed under Known limitations.
Theme switching for vibe, light/dark, font (including OpenDyslexic and Atkinson Hyperlegible), text size (four steps, up to 25% larger), and motion (auto, on, reduced) — all from the accessibility panel.
Reduced-motion respect: animations honor the operating system's prefers-reduced-motion setting by default, and any visitor can force motion fully off — or back on — from the panel.
Read-aloud using the device's built-in voices, user-triggered only, never autoplaying. A live status region announces when it's running.
Form labels are programmatic, not placeholder-only, and required fields are announced. The accessibility panel's status messages (including read-aloud state) use an aria-live region.
Plain-English copy at roughly 8th-grade reading level. We avoid agency jargon on principle.
Persistent preferences via localStorage so your settings survive a refresh and follow you across pages.

Known limitations

We'd rather list these honestly than have you find them.

Contrast checks are token-level. Our automated checks cover the color tokens of every vibe-and-mode combination, light modes included. What they don't yet cover is every rendered pairing a page can compose beyond those tokens. Any combination that doesn't clear AA gets corrected or removed.
Read-aloud voice quality depends on the visitor's device and browser. We use the Web Speech API, which means voice variety and pronunciation are out of our control. We disclose this in the panel.
No captions on read-aloud. The read-aloud feature does not currently display synchronized text. We plan to add a follow-along highlight in a future release.
Self-hosted fonts. All fonts — including OpenDyslexic and Atkinson Hyperlegible — are served first-party from emaration.ai, with no external font CDN. If a font file fails to load, the system legibility stack steps in so text never disappears.
No third-party audit yet. Disclosed above. Tracked.

If you find something not on this list, we want to know. See how to report.

Advised by lived experience

"I don't feel like I've had to overcome anything. I just do things!" — Jordan

Our co-founder Jordan Remington Williams lives with profound vision and hearing loss. He is developing a light-up white cane — early development, not yet available — after losing his vision in college. He's been a friend of Andrew's for fifteen years and is the Director of Emaration's Outreach and Community Support.

Jordan is not a consultant we hired to check a box. He is a co-founder whose daily experience shapes what we ship. Every Emaration deliverable — the written audit report, the dashboard, the emails we send you — is reviewed against the question, would this work for Jordan? If the answer is no, it doesn't ship.

That's the difference between an accessibility statement that's marketing copy and one that's a brand promise. This is the latter.

How to report a barrier

If any part of this site, an audit deliverable, or a piece of our communication blocked you from doing what you came to do, email human@emaration.ai with as much as you're comfortable sharing:

What page or document you were on.
What you were trying to do.
What happened instead.
What assistive technology, browser, and device you were using, if you know.

We don't have a business phone line, so email is the one way to reach us. If email isn't accessible to you, have someone you trust send it on your behalf and tell us what form of reply works for you. We'll match it wherever we can; the one thing we can't do today is a phone call.

You don't need to use the word "accessibility." If something on our site didn't work for you, that's enough.

What we do when you report one

This is the part most accessibility statements skip. We won't.

First reply: a human (most likely Andrew) acknowledges the report, confirms we understood what you described, and tells you what we know so far — within one business day, and we aim for the same day.
The fix: we aim to ship the fix, or send you a written remediation plan with a target date, within 30 calendar days. If the fix needs longer than that — for example, a vendor dependency — we tell you why, and what the interim workaround is.
We track every report internally, and no report closes without a written outcome to the reporter. There is no public log today.
If you escalate because we didn't respond or didn't follow through, email Jordan directly at jordan@emaration.ai with "Accessibility escalation" in the subject line. Jordan has authority to override Andrew on accessibility remediation calls.

Third-party content and tools

We use a small number of third-party services to run this site. We hold them to the same standard we hold ourselves, but we can't unilaterally change their accessibility behavior. Where they fall short, we work around them or replace them.

Cloudflare — DNS, hosting, and the Turnstile bot check that appears on our free-account and audit-intake forms. Turnstile is user-facing Cloudflare UI: usually a silent verification, sometimes a visible widget. We can't rebuild its internals; if it blocks you, that's our problem, not yours — email human@emaration.ai and we'll take it from there. (Fonts are self-hosted first-party; we do not use Google Fonts or any external font CDN.)
Stripe — membership checkout, which is live. Stripe's own statement says its checkout meets WCAG 2.1 AA; we haven't re-verified that on our live flow yet, and we'd rather name that as an open item on this statement than borrow their claim as ours. If checkout blocks you, report it and we'll finish your signup another way.
Resend (transactional email) — emails to you. We write the templates; they handle delivery. Templates are tested for screen-reader compatibility.

If a third-party tool we use blocks you from completing a task on our site, treat that as our problem and report it the same way.

Formal approvals and standards

Standard: Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, plus selected AAA criteria where supported by our High-Contrast theme.
Approach: shift-left — accessibility considered in the first design pass on every page, not retrofitted.
Approval authority: Jordan Remington Williams has accessibility veto authority over public-facing emaration.ai content and audit deliverables.
Date of this statement: August 15, 2026.
Next scheduled review: within 90 days, and after any significant site change.

The bottom line. If we say WCAG 2.1 AA and we miss it, we fix it, on the aims above. That's not a courtesy; that's the deal.

← Back to home Report a barrier