What you can report
Something may be wrong or outdated
Statements, equations, diagrams, examples, references, model/product facts or implementation behaviour.
The explanation does not land
Missing prerequisites, unexplained jumps, ambiguous wording, weak examples or an unclear relationship between concepts.
The page does not behave correctly
Broken links, navigation problems, mobile overflow, missing assets, code-display issues or inconsistent interactive behaviour.
The experience creates a barrier
Keyboard, focus, contrast, reading order, motion, labeling or other usability/accessibility concerns.
The route or activity could be stronger
Duplication, missing connections, lab sequencing, validation expectations or a better way to structure practice.
A reference or attribution needs attention
Incorrect source, broken official link, third-party identification, rights-marker or attribution-register issue.
What makes feedback useful
A strong report is specific enough that the problem can be found again without guessing.
Submit structured feedback
The fields below are intentionally concise. Only the issue description is required.
What happens after you submit feedback
The page checks the required information before confirming receipt.
Submitted feedback is handled separately from learning progress and support requests.
The page shows a reference identifier after successful receipt. Keep it if you need to refer to the submission later. Receipt does not guarantee an individual reply or a particular outcome.
Privacy & safety when reporting
Do not include passwords, API keys, payment data, government identifiers, medical records, private employer/customer data or other unnecessary sensitive information. A reply email is optional; if you are signed in, the submission may be associated with your learner account. Submitted feedback is handled under the Privacy notice.