Accessibility

What this site checks, and how.

velnoro.com is built against WCAG 2.1 AA. The checks below run automatically on every change and block anything that fails them. Automated checks are not a conformance certification, so this page states what is actually tested rather than claiming more.

The automated gate

Checked on every change, not audited afterward.

No change reaches the live site without passing these checks. Each one fails the build on its own.

  • Color contrast

    Text has sufficient contrast against the color behind it.

  • Heading order

    Headings descend one level at a time, so the page outline reads correctly.

  • Link names

    Every link has a name a screen reader can announce.

  • Image alternatives

    Images carry alternative text, or are marked decorative.

  • Page language

    Every page declares its language, so screen readers pronounce it correctly.

  • Page descriptions

    Every page describes itself, for search results and assistive tooling alike.

  • Page titles

    Every page has a title that says what it is.

On top of the individual checks, the accessibility score must be perfect on every page in the audit list, this one included.

Contrast is tested where the colors are defined.

The palette lives in a single file, and a build-time test reads that file and checks its text and background pairings against the WCAG AA thresholds: 4.5 to 1 for body text and 3 to 1 for large text. A color change that breaks a pairing fails the build before it ships. The same test records which pairings fail on purpose, which is why some colors are only ever used as fills and never as text.

What is checked by hand.

Alongside the automated gate, changes are checked as working practice rather than as a guarantee:

  • A keyboard-only pass: everything reachable without a mouse, panels close on Escape, and focus returns to where it was.
  • A pass with JavaScript disabled: every page renders its full content without scripts.
  • Layout walks at desktop, tablet, and phone widths.

What this site cannot control.

The booking page embeds the Cal.com scheduling widget. The scheduler interface belongs to Cal.com: it sits outside the checks described above, and with JavaScript off the page offers a direct link to the same booking page instead. Everything around that widget goes through the same gate as the rest of the site.

Report a barrier.

If part of this site does not work with a screen reader, a keyboard, or any other assistive technology, an email naming the page and the barrier is enough for it to be investigated and fixed.