Accessibility statement
Hyrizen wants everyone to be able to use this site. Here is what we do, how we test, and how to reach us if something is in the way.
Published
Conformance target
hyrizen.com is built to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Where we fall short, we say so below and fix it.
What we do
- Native semantics first: real headings in order, one main landmark, real links and buttons, labels on every form field.
- Keyboard operability throughout, visible focus that is never removed, and a skip link on every page.
- Text contrast of at least 4.5:1 on every surface, including translucent “glass” panels, which are checked in our build against their worst-case background.
- Respect for
prefers-reduced-motion: all animation and background motion is disabled when you ask for it. - Content that reflows to 320 px wide without horizontal scrolling and text that can be resized to 200%.
- Tap targets of at least 44×44 CSS pixels.
- No accessibility overlay widgets; we fix the underlying HTML instead.
How we test
Every build runs axe-core over every page (structural rules) and a token-level contrast check; releases are spot-checked by keyboard only, with VoiceOver on macOS and iOS, and at 200% zoom. Automated tools catch roughly half of real problems, so we treat reports from people as the more important signal.
Known limitations
The free AI-visibility scan renders its results with client-side script; the results are announced to assistive technology but the tool is not usable without JavaScript. Third-party components (Cloudflare Turnstile) follow their vendors’ accessibility support.
Feedback
If any part of this site is hard to use, email hello@hyrizen.com with the page address and what happened. We reply within two business days and fix confirmed problems in the next release.