Corrections & Feedback

The quickest way to make a report useful is to show the difference between what the page says it does and what actually happened. A result that seems surprising may come from an uncertain input, a browser limitation or an error in the application. We need enough detail to tell those apart.

Report a reproducible problem

• Copy the exact tool URL, including the relevant tool name rather than only the homepage.
• State your device, operating system and browser if you know them. Browser versions help when the behavior is specific to one environment.
• List the steps in order, including the inputs and units. Use invented or redacted data when the real values are personal.
• Describe the result you saw and what you expected instead. If the issue disappears after a reset or reload, mention that too.
• Explain whether the problem happens consistently or only under a particular condition, such as a narrow window or denied permission.

A useful calculation report might say: “In PPI Calculator, I entered 1920 × 1080 and a 24-inch diagonal. I expected about 91.8 PPI, but the page displayed a different value.” That gives a testable scenario without requiring a photograph of a device or an account login.

Report a factual correction

Quote the specific statement or name the field you believe is outdated. Add a primary source where possible and explain whether it concerns a different model, platform, region or version. A general link to a company homepage may not support the particular correction.

For game tools, distinguish official information from a personal entry. Adding a speculative value to a personal workspace does not make it a correction to the sourced snapshot. Missing information can remain unavailable when it cannot yet be verified.

Accessibility and suggestions

For an accessibility issue, identify the task and the control that prevents you from completing it. Include relevant keyboard steps, browser behavior or assistive technology if you are comfortable doing so. Describe the barrier rather than assuming the cause.

For an improvement, explain the job you want to accomplish. A concrete use case helps more than a request to make a tool “better.” We may need to keep a limitation explicit when the browser or available data cannot support the requested function.

Send the report

Use the contact form and identify Technical problem, Calculation, Outdated information or Accessibility in the subject as appropriate. The same form handles general suggestions and copyright concerns. The form accepts text and source URLs, not attachments. Do not send passwords, payment details or a full personal workspace export in the first report.

What happens next

A report is reviewed against the described behavior, the relevant inputs and any supporting source. We may ask for clarification if a reply address is available. A confirmed issue can lead to a code fix, a source update, a clearer limitation or a correction to the instructions.

There is no promised investigation or resolution deadline. Acknowledging receipt does not mean that a reported cause has been confirmed. When a substantive correction changes how earlier information should be interpreted, the affected page should make that change clear rather than quietly treating it as the original version.