Contact and corrections

Use the channel that supplied this release

This static release does not invent an email address and does not run a server-side contact form. Submit the report through the repository issue tracker, deployment-owner contact, or distribution channel from which you received BarcodeOpsKit. If that channel does not publish a destination, retain the report template below and ask the site operator to provide one. This page will name a direct channel only after the operator verifies it.

What to include

• Issue category: content, standards, accessibility, privacy, security, or software.
• The public page path and visible heading.
• The exact statement or step that appears wrong.
• Expected behavior and a concise reproduction using synthetic data.
• For standards corrections, the primary source title, version, section, and URL.
• Browser and assistive technology versions when relevant.

Do not include operational data

Never send a real GTIN, UPC, EAN, GLN, SSCC, GS1 element string, Digital Link, scan result, CSV row, uploaded filename, label, workspace backup, customer record, secret, token, or camera image. Replace values with a clearly labelled synthetic example. BarcodeOpsKit cannot determine registration or ownership from a submitted number.

How corrections are handled

A standards-dependent correction should identify the authoritative source before code or explanatory content changes. Calculation and parser fixes require a regression test. Content changes retain source and review metadata. Accessibility and privacy reports are assessed against the stated target and data boundary. The public changelog records user-visible corrections once evidence is available.