Accessibility statement

We want everyone to be able to make, change and scan ovbq codes, including people who use a screen reader, a keyboard, zoom or a phone in bright sun.

Our target

We design and build ovbq to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

What we do

• Body text is 18 pixels and never smaller than 16. Text and controls meet the contrast levels in WCAG.
• Every control is a standard link, button or form field, so it works with a keyboard, and the focused item always has a thick, clear outline.
• We design controls to be easy to tap. Links in text are underlined.
• Pages work at 400% zoom and on screens 320 pixels wide without sideways scrolling, except the wide plan and compare tables, which scroll inside their own box.
• Every field has a label. The unit menus next to number fields are labeled for screen readers. When something is wrong, a list at the top of the form says what to fix and links to each field.
• Status is shown with an icon and a word, never by color alone. The logo and the boxes you tap are marked by their shape and border instead.
• Nothing moves, flashes or changes by itself, and no message disappears. No pop-ups open on their own. The only dialog is the delete confirmation, which you open yourself.
• The scan chart has a summary sentence and a "Show as a table" option.
• The free QR code maker is built to work without JavaScript: the "Update preview" button and the downloads use plain forms.
• We write in plain language.

Known limits

• Sign-in links expire after 15 minutes for safety. You can ask for a new one at any time, within the hourly limit.
• On phones, the plan comparison shows one plan at a time next to the features, and the compare tables stack each row. Where a wide table (the plan and compare tables) doesn't fit, as in older browsers or with large text, it scrolls sideways inside its own labeled box.
• Some downloads may be blocked by our web host's security filter, with or without JavaScript. If you see “That didn't go through,” go back and try again. If it keeps happening, write to us and tell us which page you were on and what you were trying to do.
• ovbq has not yet had an independent accessibility audit.

Tell us about a barrier

If something on ovbq is hard to use, please write to hello@ovbq.com. Tell us the page and what went wrong. We aim to reply within 2 business days and fix confirmed barriers within 30.

This statement was written on October 20, 2026, and updated on October 25, 2026.