Fact-Checking Policy
Last updated: September 19, 2026. Our guides make two kinds of factual claims: claims about how web technologies and browsers work, and claims about how our own games behave. This page explains how each kind is checked before publication and how we handle mistakes afterward.
What we check
Before a guide or page is published, the reviewing editor identifies every statement that could be true or false, as opposed to opinion or advice. Typical examples include:
- How a browser API behaves, such as when
requestAnimationFramecallbacks run or whatlocalStoragecan store. - What an accessibility guideline requires.
- How a specific Jumping Arcade game works: its controls, platforms, hazards, scoring and what ends a run.
- Descriptions of our own practices, such as what data the site stores.
Each statement must be supported by one of the source types below, or it is rewritten or removed.
Checking technical claims
For claims about web technologies, we go to primary and authoritative references rather than blog posts or forum answers:
- MDN Web Docs for browser APIs such as the Canvas API, requestAnimationFrame, localStorage, the Web Audio API, pointer events and keyboard event keys.
- Web specifications, including the WHATWG HTML Living Standard and relevant W3C specifications, when precise behavior matters.
- Web Content Accessibility Guidelines, specifically WCAG 2.2, for any statement about accessibility requirements.
Where browsers differ, we say so rather than presenting one browser's behavior as universal. If a claim cannot be confirmed from these sources, we do not publish it as fact.
Checking gameplay claims
Claims about our games are verified by playing them. If a guide says a platform breaks after one bounce, a meter speeds up over time or a combo multiplier resets after a wasted jump, an editor confirms it in the current version of the game. Where it matters, controls are checked with both keyboard and touch input.
We also check that general gameplay advice fits the games it is attached to. A tip about double jumping, for example, should not be linked to a game that has no double jump.
Source types we use
| Type of claim | Source we rely on |
|---|---|
| Browser API behavior | MDN Web Docs reference pages |
| HTML and platform behavior | WHATWG HTML Living Standard and W3C specifications |
| Accessibility requirements | WCAG 2.2 published by the W3C |
| How our games behave | Hands-on play of the current published version |
| Our own data practices | The site's code and our Privacy and Cookie Policies |
| Third-party services, such as advertising | The provider's own official policy pages |
What we don't do
- We do not fabricate sources, quotes, studies or statistics.
- We do not cite a source we have not read, or link to a page to support a claim it does not make.
- We do not treat output from AI drafting tools as a source. Anything drafted with such tools is verified like any other text, as described in our Editorial Policy.
- We do not present game design conventions as scientific findings.
Corrections process
- Report: anyone can report a possible error by emailing [contact email to be published]. Please include the page address, the exact statement and, if possible, a source that supports the correction. The contact page lists what helps most.
- Review: an editor checks the statement against the relevant source or by playing the game.
- Correct: if the statement is wrong or misleading, the page is corrected and its updated date changes for substantive corrections.
- Follow through: we check related guides and game pages for the same mistake and fix those too.
If we conclude that the original statement is accurate, we keep it, and may clarify the wording if the report showed it was confusing.
Related policies
This policy works alongside our Editorial Policy, which covers originality, human review and independence from advertising, and our About page, which describes how games are tested before publishing.