Send feedback
This site is maintained by one person, and feedback is how problems that the automated tests cannot see get found: a result that is technically correct but confusing, a page that assumes knowledge the reader does not have, a tool that is missing for a task people actually do. Every message is read. Not every message can be answered, but every one is recorded and triaged.
- No account needed
- Email optional
- Every message is triaged
Tell us what happened
The page you are on is filled in automatically; change it if the report is about another page. Be specific enough that the problem can be reproduced without a follow-up question.
What makes a report actionable
The most useful reports include three things: the page (it is filled in automatically, and you can correct it in the form), what you did, and what you expected instead. If a result was wrong, the exact input matters — without it the case cannot be reproduced or added to the test suite. A screenshot helps when the problem is visual; a sentence or two of context is usually enough when it is not.
- Broken: the control that did nothing, the error message, the browser and device.
- Wrong explanation: the sentence and, if you know it, the standard or source that contradicts it.
- Missing tool: the task you were trying to complete, not just the tool name — the task is what decides whether it belongs here.
- Accessibility: the page, the assistive technology and what happened.
What not to send
Do not paste passwords, API keys, private keys, session tokens or personal data into the feedback form. The message is stored on the server so it can be reviewed later; it is not encrypted at rest beyond the server's disk, and it is not a secure channel. If a problem can only be shown with sensitive input, describe the shape of the input instead, or use the contact address and ask how to share it.
What happens to a message
Messages are stored as a small structured record: the time, the page path, the category, the message and — only if you provide it — an email address. The IP address is not stored. The record is used to reproduce the problem, to decide whether it is a bug, a documentation fix or a new tool, and then to close the loop in the test suite where possible. Feedback is not published and is not shared with third parties.
Records are kept for up to twelve months and then removed. If you leave an email, it is used only to reply to that report; it is not added to a list and not used for marketing. You can ask for a record to be deleted by writing to the contact address, quoting the page and approximate time.
Response expectations
This is not a support desk. Reports are read in batches, and a fix may take days or weeks depending on severity and whether it needs a new test. A confirmed bug is added to the test set before it is fixed, so the same problem cannot return silently; a correction to an explanation is checked against the engine and the cited standard before the page changes. If you need a reply, leave an email — a report without one is still read, but there is no way to ask you a follow-up question.
For account, advertising or legal questions, use the contact page instead; those are not handled through this form. For a security issue, say so in the first line and avoid including exploit details in the message.