Accessibility

We want this website to be usable by a broad range of people, including people who navigate by keyboard, use a screen reader, or need reduced motion or higher contrast. Accessibility here is an ongoing engineering practice, not a one-time certification — we are not claiming full compliance with any accessibility standard, and we keep improving as we find gaps.

• Every canonical public page is scanned with an automated accessibility checker (axe, WCAG 2.0/2.1 A and AA rules) as part of our test suite, and the build fails on any critical or serious violation.
• Skip links let keyboard users jump straight to the main content or the navigation, bypassing repeated header content.
• A visible focus outline is enforced site-wide for every interactive element — links, buttons, form fields — so keyboard focus is never invisible.
• Pages use semantic landmarks and headings (nav, main, section with labelled headings) rather than generic, unlabelled containers, and our tests check that heading levels are not skipped.
• Motion respects your system’s reduced-motion preference; when it is set, animation is minimized, and we test that this preference is actually honored.
• Decorative icons are hidden from assistive technology, while icons that convey information carry accessible text.
• Layouts are responsive rather than a separate degraded mobile experience.

Automated testing catches a meaningful share of issues but not everything — color-contrast edge cases in illustrative diagrams, less common screen-reader interaction patterns, and third-party embedded content are harder to fully verify automatically. We treat a specific, reported problem as more useful than a general compliance claim, and we prioritize fixes for the pages people actually use to evaluate or contact Veldarium.

If you hit a barrier using this site, tell us what page you were on, what you were trying to do, and what happened, at chris@veldarium.com. We read every message directly and will do what we reasonably can to fix a genuine barrier.