qr-code-build

Legal

Accessibility statement

What has been done, what is still imperfect, and how to tell us when something does not work for you.

Short answer

This site aims to meet WCAG 2.2 Level AA. Pages use semantic HTML, work by keyboard, respect reduced-motion preferences, and remain usable at 200% zoom and on small screens. Known limitations are listed below along with how to report anything that does not work for you.

Contents
What has been done

Measures in place

  • Semantic HTML: real headings in order, lists, tables with header cells, and landmark regions.
  • A skip link to the main content, and a visible focus outline on every interactive element.
  • Full keyboard operation, including the generator's type tabs, the design drawer and the image reader's drop zone.
  • Form fields with associated labels, and help text tied to the field it describes.
  • Text contrast meeting AA against its background, with interactive states not relying on colour alone.
  • Respect for prefers-reduced-motion: transitions are effectively disabled where requested.
  • Responsive layout down to 320px with no horizontal scrolling, and 16px form inputs so mobile browsers do not zoom unexpectedly.
  • Text that reflows at 200% zoom without loss of content or function.
  • Alternative text on meaningful images, and an accessible name on the QR preview.
Known limitations

Where it falls short

Stated honestly rather than omitted:

  • The generated QR code is inherently visual. It is a machine-readable image with no text equivalent that would convey the same function. The live specification readout beside it describes the code in text — version, grid, error correction, byte count and minimum print size — which is the closest meaningful equivalent.
  • The colour pickers use the browser's native colour control, whose accessibility varies by platform. Colour values can also be typed as hex where the browser allows it.
  • Reading a QR code from an image requires uploading a picture, which assumes some visual context about the code being scanned.
  • Wide reference tables, such as the 40-version capacity table, scroll horizontally on narrow screens. The data is fully available but requires scrolling.

We have not commissioned a formal third-party audit. This statement reflects our own testing, so it is a self-assessment rather than a certified conformance claim.

Reporting

Tell us if something does not work

If you find an accessibility barrier, email contact@qr-code-build.com with the page address and a description of the problem, including the assistive technology and browser you were using if relevant.

We aim to respond within five working days. Accessibility fixes are prioritised over feature work, and the page review date is updated when one is made.

If you are not satisfied with the response, tell us why and we will look at it again. Accessibility is treated as a defect to fix, not a feature request.

Questions

Frequently asked

Does this site meet WCAG 2.2 AA?
That is the target, and the measures listed above are implemented against it. This is a self-assessment, not an audited conformance claim, and known limitations are listed openly.
Can I use the generator with a keyboard only?
Yes. All controls including the type tabs, design drawer and file inputs are keyboard operable with a visible focus indicator.
Does the site work with a screen reader?
The pages use semantic HTML with labelled form fields and landmark regions. The QR image itself is visual by nature; the text readout beside it conveys the code's properties.
How do I report an accessibility problem?
Email contact@qr-code-build.com with the page address and a description. We aim to reply within five working days.
Next

Keep going

Last reviewed 24 August 2026 · Checked by the QR Code Builder team