Accessibility

A site that works for everyone.

Last updated: May 29, 2026

Eurema builds websites — it would be contradictory not to apply to our own sites the rules we apply to our clients'. This page documents where we meet WCAG 2.1 level AA, where we know we still fall short, and how to report issues.

What's covered

  • Semantic HTML — hierarchical headings, landmarks (header, main, nav, footer), semantic lists. Screen readers can navigate the structure.
  • Color contrast — body text on cream background passes AA (≥4.5:1). The honey accent (#F99C00) is used for emphasis but never as the sole carrier of critical information.
  • Visible keyboard focus — all links and buttons have :focus-visible state with honey outline.
  • Form labels — all inputs have associated label or aria-label.
  • Alt text — decorative images have alt=""; informative ones (founder photo, demo screenshots) have descriptions.
  • prefers-reduced-motion — all animations disable automatically when the user requests it in their OS.
  • Declared language — lang="en" on HTML so screen readers pronounce correctly.
  • Zoom up to 200% without breaking layout (tested).

What we're improving

Honest acknowledgements:

  • Pixel art is decorative with aria-hidden, but some scenes (industry street, Academy scene) could have a long description alternative for screen reader users. In backlog.
  • The language switcher uses globe icon + "EN/ES" text — passes AA but we could add a more descriptive aria-label.
  • Academy videos (when live) will need captions and transcripts. Part of the scope when Series ships.

Technologies we test with

  • NVDA and VoiceOver (screen readers).
  • Lighthouse Accessibility audit — target ≥95.
  • axe DevTools — automated audit on every deploy.
  • 100% keyboard navigation — Tab, Shift+Tab, Enter, Esc.

Report an issue

If you find something that doesn't work for you or someone you know, write us:

Email: [email protected] (subject: "Accessibility")
WhatsApp: +52 81 1532 9429

We commit to respond in ≤5 business days and, if the fix is feasible in code, apply it on the next release (typically the same week).

Why we publish this

Most legal accessibility pages are boilerplate copied from a template. This one isn't. Eurema is a small team — one human (Luis) operating with AI agents — and accessibility is a real commitment, not a checkbox. If something doesn't work for you, I respond personally.

Luis Guzmán — Founder, Eurema