100-day trial Free returns

Home Accessibility

Accessibility

Last updated September 1, 2026

We want this site usable by everyone, including people using screen readers, keyboard navigation, magnification, or browsing with JavaScript disabled.

What we target

WCAG 2.2 Level AA.

What has actually been done

  • Color contrast — every text and background pair used on the site has been measured. Body text meets or exceeds 4.5:1; interface elements meet 3:1. The primary buttons are a deliberately darker green than the brand color for this reason.
  • Keyboard — every interactive element is reachable and operable by keyboard, with a visible focus indicator that inverts to stay visible on dark sections. A skip link moves focus, not just the scroll position.
  • Screen readers — one h1 per page and no skipped heading levels; the homepage and fit-page comparison tables use proper row and column headers (the smaller tables inside articles use header rows only); star ratings expose a text rating rather than star glyphs; the off-screen buy bar is removed from the tab order rather than hidden with aria-hidden.
  • Without JavaScript — the site renders completely. No content depends on scripts to become visible.
  • Reduced motion — all animation and smooth scrolling are disabled when your system requests reduced motion.
  • Zoom and reflow — the layout reflows to 320px and text can be enlarged without content being clipped. Expanded FAQ answers size to their content, so nothing is cut off at large text sizes.

Known gaps

  • Every image on the site carries a written alt description. Most diagrams are SVG images with labels drawn into the picture. Screen readers get the alt text, which summarizes each diagram’s labels rather than reproducing every one; the fit table and the spec list carry the same numbers as text.
  • The site has been tested with automated tooling and manual keyboard checks, but not yet with users of assistive technology. That is the test that actually counts.

Found a barrier?

Please tell us: max@aylio.com. Describe the page and what happened, and we will fix it. Accessibility bugs go to the front of the queue.