Accessibility Statement

We want everyone to be able to read this site, use the math tool, and reach us. That holds for any device and any assistive tech. This page says what we have done. It also says how to tell us when we have fallen short.

1. The Standard We Build To

We build and test this site to the Web Content Accessibility Guidelines (WCAG) 2.1, at Level AA. The US Department of Justice points firms to WCAG for web access under the ADA. We aim to meet it. We claim no certificate, and no outside firm has audited us yet.

2. What We Have Done

• We build each page with a skip link and one main landmark. The nav is labeled. The headings run in a logical order.
• We test the color contrast by machine before each release. We set normal text to meet at least 4.5 to 1. We set large text and controls to meet at least 3 to 1.
• You can work the whole site from a keyboard, in a sensible order. A focus outline shows on each control you land on.
• Form fields have labels you can see and clear error messages. Screen readers call out those errors. Each field carries the standard hints your browser uses to fill it in. The consent box is not pre-checked.
• Graphics that are there for looks are hidden from assistive tech. Each image that carries meaning has text with it that says the same thing.
• With reduce motion on, the moving background stops. So does the text animation.
• You can resize text to 200% and the layout still works. It works on phones, tablets, and desktops, with no sideways scrolling.
• The FAQ uses built-in sections that open and close. They work with a keyboard and a screen reader, with no custom script.

3. What Does Not Work Yet

• The booking widget on our Book a 15-minute call page comes from Cal.com. We do not control how well it works for you. If it does not, call (210) 504‑6921 or email topher@velosystems.io. We will book the time with you.
• The example text thread on the home page is a picture. The text around it says the same thing.

4. How We Test

This site is checked with automated and manual tests before each release. We run the machine checks at desktop and phone sizes. They cover axe-core rules for WCAG 2.1 A and AA. They look at color contrast, at keyboard order, and at where the focus ring lands. They also check that the HTML on each page is valid. Then we read the results by hand. Last machine check: October 3, 2026.

5. Tell Us What Is Broken

Is any part of this site hard to use? Do you need what we say here in another format? Contact us. We will work to fix it or send it to you another way. We reply within five business days and tell you when we can fix it.

Email: topher@velosystems.io
Phone: (210) 504‑6921