How to Report a Bug or Suggest an Improvement on chemequations.com

Updated

chemequations.com provides two direct feedback entry points on its page: "Found a bug?" and "Do you know what to improve?". Use the first if something on the site is broken or behaving incorrectly, and the second if you want to propose a change, addition, or usability improvement. Both are plain links on the main page — no account or login is mentioned anywhere in the available site information, so you can reach them directly from the homepage.

Where the feedback links are

The site's visible page content includes this line near the bottom:

Found a bug? Do you know what to improve? © Michal Punčochář

So the two links sit together in the footer area of the page, next to the copyright notice. The copyright line credits Michal Punčochář, which indicates the site is maintained by an individual developer rather than a large support team — useful context for setting expectations about how feedback is handled.

Which link to use

Your situation Link to use
A page, button, or calculation is broken or gives a wrong result Found a bug?
You want a new feature, clearer wording, or a design change Do you know what to improve?
You are unsure whether it is a bug or a suggestion Either one — describe the behavior and what you expected

The distinction matters mainly for how the maintainer triages the report, not for whether you can submit it.

What to include in your message

The site does not publish a form structure or required fields, so there is no fixed template to follow. What makes feedback actionable is the same regardless of the channel:

  • What you did — the exact reaction, equation, or search you entered.
  • What you expected — the balanced result, the page you expected to load, or the behavior you assumed.
  • What actually happened — the wrong output, the error, or the missing feature.
  • Your environment — browser and device, since the site itself warns that some features depend on JavaScript.

That last point is worth emphasizing. The page states:

Witout JavaScript enabled some features might not work correctly.

If a feature appears broken, first confirm JavaScript is enabled in your browser and try reloading. If it still fails with JavaScript on, that is a genuine bug worth reporting — and mentioning that you already checked JavaScript saves the maintainer a round of back-and-forth.

A concrete example

Suppose you enter a reaction, the page returns a balanced equation, but one coefficient looks wrong to you. A useful bug report would say: the reaction you typed, the coefficient the site produced, the coefficient you calculated by hand, and the browser you used. A useful improvement suggestion would say: "the input box would be easier to use if it accepted the arrow symbol directly" — a specific, testable request rather than a general complaint.

Practical notes

  • The available site information does not describe a contact form, email address, or response time, so do not assume a particular turnaround.
  • Because the site is credited to a single maintainer, concise and specific reports are more likely to be acted on than long ones.
  • If your issue is that a feature "does not work," check the JavaScript requirement before reporting it as a bug.