Skip to content

Contact

Tell me what broke.

Bug reports, awkward edge cases, and tool suggestions are all useful. One person reads the inbox, so a clear message with a reproducible example gets a faster answer than a one-line “it doesn’t work”.

Email

[email protected]

Replies usually arrive within two working days. There is no support portal and no ticket number.

Good to know

More than a bug box.

This is a small, independent project. The same inbox handles bugs, corrections, accessibility reports, and ideas, so a specific subject line helps sort the useful details from the noise.

Accessibility reports

If a control is hard to reach by keyboard, a label is missing, or text is difficult to read, treat it as a bug. Include the page, browser, and the step where it happens.

Corrections

Explanations, limits, and examples should be accurate. Send the page and the sentence that is wrong. Corrections are prioritized over new features.

Tool requests

Describe the text problem and show a small input and the output you expected. That is more useful than a long specification, and it keeps the toolkit focused.